Re: [jbosstools-dev] Versions bump policy change
On 28 Feb 2017, at 18:11, Jean-Francois Maury wrote:
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
sounds awesome if you guys found a way to deal with having to manually
keep these
from not overlapping and avoid rerelasing different bits with the same
version number.
Will this mean that builds and release now only update the actual
changed plugins ?
and download diff will be smaller too ?
btw. how come stopping to do the 3.3.0, 3.3.100 etc. as is standard in
p2/eclipse ?
/max
http://about.me/maxandersen