[rules-dev] JBoss versioning policy - community 6.1 vs 7.0

[Mark Proctor]

This quote comes to mind:
http://www.brainyquote.com/quotes/quotes/a/alfredlord101361.html

On Wed, Feb 19, 2014 at 9:08 AM, Wolfgang Laun <wolfgang.laun at gmail.com>wrote:

> 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 at 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 at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/rules-dev
> >
> _______________________________________________
> rules-dev mailing list
> rules-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20140219/1447631a/attachment.html