[jbosstools-dev] Working on 4.3.1/4.4.0

Alexey Kazakov alkazako at redhat.com
Tue Sep 22 17:14:36 EDT 2015


Hi,

Just a reminder that the jbosstools-4.3.x branch is still frozen and 
will remain frozen until we release JBT 4.3.0.Final (should happen in 
two weeks or later if we have to postpone it).

If you have something you want to fix for the future versions then please:

*a. If your change is something that should be fixed only for JBT 4.4*, 
for example some big changes or Eclipse Neon related fixed/updates then:
a.1. Create a PR for master. Apply it. Resolve the issue for JBT 
4.4.0.Alpha1. (don't forget to update the version of your component if 
you have not done it yet).

*b. If you have something that should be fixed in both JBT 4.4 (Eclipse 
Neon) and JBT 4.3.1* (maintenance release for Eclipse Mars) then:
b.1. Fix it in master. See a.1.
b.2.1. Create a PR for jbosstools-4.3.x and wait for that branch to be 
open for 4.3.1 development. You should keep your JIRA open until both PR 
are merged.
or if you really need some open branch to continue working on 4.3.1 
issues (for example the OpenShift team needs it) then you have the 
following option:
b.2.2. Create a new jbosstools-4.3.1.x branch from jbosstools-4.3.x, 
work with that to fix all needed issues (create a PR, apply after 
someone's review, resolve the jira, all usual stuff). And create a JIRA 
for JBT 4.3.1 which says the 4.3.1.x branch should be merged to 4.3.x. 
When the main 4.3.x branch is open, then you will be able to merge the 
branches and continue working on the main 4.3.x branch directly.

I hope it makes sense.

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150922/42d968a3/attachment-0001.html 


More information about the jbosstools-dev mailing list