[jbosstools-dev] Versions bump policy change

Jean-Francois Maury jmaury at redhat.com
Tue Feb 28 12:11:21 EST 2017


Hello,

as we branched for Oxygen, we now have two different branches to maintain
and as we are pushed changes in the code base, we need to upversion the
components.
In order to be better aligned with OSGI/P2, we decided to change a little
how the bump is managed.
Previously, all sub-components of a component (eg jbosstools-openshift)
were upversioned as soon as a single sub component is modified). We will
upversion only the sub component that has changed.
For master, the minor will be incremented and for 4.4.x, the micro will be
increment.

As an example, we need to update org.jboss.tools.openshift.client in both
branches and as OpenShift is 3.3.2, this will give:

   - master: org.jboss.tools.openshift.client only will switch to 3.4.0
   - 4.4.x: org.jboss.tools.openshift.client only will switch to 3.3.3

We will experiment this during 4.4.4.AM1 and revisit if we found too many
problems
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20170228/beb53f7a/attachment.html 


More information about the jbosstools-dev mailing list