ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.0.Final ]
7:12 p.m.
Component leads, please tag your repositories!
$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
jbosstools, also often called origin
$ git checkout FETCH_HEAD
$ git tag jbosstools-4.2.0.Final
$ git push jbosstools jbosstools-4.2.0.Final
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
8:12 p.m.
base, jst, javaee - done.
So, jbosstools-4.2.x is now open for 4.2.1 development, correct?
On 10/20/2014 05:12 PM, Nick Boldt wrote:
Component leads, please tag your repositories!
$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
jbosstools, also often called origin
$ git checkout FETCH_HEAD
$ git tag jbosstools-4.2.0.Final
$ git push jbosstools jbosstools-4.2.0.Final
8:20 a.m.
On 10/21/2014 03:12 AM, Alexey Kazakov wrote:
base, jst, javaee - done.
So, jbosstools-4.2.x is now open for 4.2.1 development, correct?
Yes, it should be
good to go.
But changes on this branch should really be associated to jira entries
targeting 4.2.1, use and link pull requests, and get a positive review
before merging.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
12:07 p.m.
Also, until JBDS 8.0.0.GA is actually live, all the JBT component builds
should stay disabled. So anything you DO push (after opening a JIRA,
attaching a PR and getting approvals) won't be built in Jenkins just yet.
Please ensure you've built locally before pushing to the 4.2.x branch.
N
On 10/21/2014 09:20 AM, Mickael Istria wrote:
On 10/21/2014 03:12 AM, Alexey Kazakov wrote:
> base, jst, javaee - done.
> So, jbosstools-4.2.x is now open for 4.2.1 development, correct?
Yes, it should be good to go.
But changes on this branch should really be associated to jira entries
targeting 4.2.1, use and link pull requests, and get a positive review
before merging.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
12:09 p.m.
On 10/21/2014 06:20 AM, Mickael Istria wrote:
On 10/21/2014 03:12 AM, Alexey Kazakov wrote:
> base, jst, javaee - done.
> So, jbosstools-4.2.x is now open for 4.2.1 development, correct?
Yes, it should be good to go.
But changes on this branch should really be associated to jira entries
targeting 4.2.1, use and link pull requests, and get a positive review
before merging.
Are you saying I have to get the PR approved by Max, Denis or Fred
before I can merge it to 4.2.x for JBT 4.2.1?
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
2:52 a.m.
On 10/21/2014 07:09 PM, Alexey Kazakov wrote:
On 10/21/2014 06:20 AM, Mickael Istria wrote:
> On 10/21/2014 03:12 AM, Alexey Kazakov wrote:
>> base, jst, javaee - done.
>> So, jbosstools-4.2.x is now open for 4.2.1 development, correct?
> Yes, it should be good to go.
> But changes on this branch should really be associated to jira
> entries targeting 4.2.1, use and link pull requests, and get a
> positive review before merging.
Are you saying I have to get the PR approved by Max, Denis or Fred
before I can merge it to 4.2.x for JBT 4.2.1?
I think that the Jira needs to be at
least considered as important
enough to require a change in 4.2.x.
About the PR, the better seems to be that you get it reviewed by someone
else who has good understanding of the code, so that there are more
chances reviewer catches actual issues.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
8:12 a.m.
Done for WebServices and LiveReload
Best regards,
/Xavier
On 21 Oct 2014, at 02:12, Nick Boldt <nboldt(a)redhat.com> wrote:
Component leads, please tag your repositories!
$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
jbosstools, also often called origin
$ git checkout FETCH_HEAD
$ git tag jbosstools-4.2.0.Final
$ git push jbosstools jbosstools-4.2.0.Final
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
8:31 a.m.
VPE and BrowserSim - done
On 10/21/2014 3:12 AM, Nick Boldt wrote:
Component leads, please tag your repositories!
$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
jbosstools, also often called origin
$ git checkout FETCH_HEAD
$ git tag jbosstools-4.2.0.Final
$ git push jbosstools jbosstools-4.2.0.Final
8:39 a.m.
Done for arquillian, birt and portlet.
Snjeza
On 10/21/2014 2:12 AM, Nick Boldt wrote:
Component leads, please tag your repositories!
$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
jbosstools, also often called origin
$ git checkout FETCH_HEAD
$ git tag jbosstools-4.2.0.Final
$ git push jbosstools jbosstools-4.2.0.Final
9:01 a.m.
Done for Central
Le 20 oct. 2014 à 20:12, Nick Boldt <nboldt(a)redhat.com> a écrit
:
Component leads, please tag your repositories!
$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
jbosstools, also often called origin
$ git checkout FETCH_HEAD
$ git tag jbosstools-4.2.0.Final
$ git push jbosstools jbosstools-4.2.0.Final
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
10:24 a.m.
Freemarker is tagged.
On 10/20/2014 05:12 PM, Nick Boldt wrote:
Component leads, please tag your repositories!
$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
jbosstools, also often called origin
$ git checkout FETCH_HEAD
$ git tag jbosstools-4.2.0.Final
$ git push jbosstools jbosstools-4.2.0.Final
4:12 a.m.
On 10/21/2014 02:12 AM, Nick Boldt wrote:
Component leads, please tag your repositories!
$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
jbosstools, also often called origin
$ git checkout FETCH_HEAD
$ git tag jbosstools-4.2.0.Final
$ git push jbosstools jbosstools-4.2.0.Final
done for openshift
3488
days inactive
3489
days old
jbosstools-dev@lists.jboss.org
11 comments
9 participants
participants (9)
-
Alexey Kazakov -
André Dietisheim -
Denis Golovin -
Fred Bricon -
Konstantin Marmalyukov -
Mickael Istria -
Nick Boldt -
Snjezana Peco -
Xavier Coulon