Re: [rules-dev] JBoss versioning policy - community 6.1 vs 7.0
An absolutely unusual reason for incrementing a major version number,
which traditionally is only done when some major change is being made.
And I don't think that a difference of 1.0 will make a difference in
people's minds.
-W
On 19/02/2014, Mark Proctor <mproctor(a)codehaus.org> wrote:
I'm providing some information on planned version policy changes
within
JBoss, that will most likely impact our next community release.
Currently the project vs product version numbering is considered confusing
by some people; especially when both the project and the product are on the
same major version number. One of the ways JBoss wishes to address this is
for the community major version to automatically increment just prior to the
product release - if the community is on the same version. For example as
JBoss BRMS 6.0 is about to release, with community currently also on 6.0 the
next community release would be required to move to 7.0, instead of 6.1.
Community can then do 7.1, 7.2, 7.3 etc until the product shifts to 7.0. At
which point the community much shift to 8.0.
Mark
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev