<div dir="ltr"><div>This quote comes to mind:<br></div><div><a href="http://www.brainyquote.com/quotes/quotes/a/alfredlord101361.html">http://www.brainyquote.com/quotes/quotes/a/alfredlord101361.html</a></div><div class="gmail_extra">
<br><div class="gmail_quote">On Wed, Feb 19, 2014 at 9:08 AM, Wolfgang Laun <span dir="ltr"><<a href="mailto:wolfgang.laun@gmail.com" target="_blank">wolfgang.laun@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
An absolutely unusual reason for incrementing a major version number,<br>
which traditionally is only done when some major change is being made.<br>
<br>
And I don't think that a difference of 1.0 will make a difference in<br>
people's minds.<br>
<br>
-W<br>
<div><div class="h5"><br>
<br>
<br>
<br>
On 19/02/2014, Mark Proctor <<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>> wrote:<br>
> I'm providing some information on planned version policy changes within<br>
> JBoss, that will most likely impact our next community release.<br>
><br>
> Currently the project vs product version numbering is considered confusing<br>
> by some people; especially when both the project and the product are on the<br>
> same major version number. One of the ways JBoss wishes to address this is<br>
> for the community major version to automatically increment just prior to the<br>
> product release - if the community is on the same version. For example as<br>
> JBoss BRMS 6.0 is about to release, with community currently also on 6.0 the<br>
> next community release would be required to move to 7.0, instead of 6.1.<br>
> Community can then do 7.1, 7.2, 7.3 etc until the product shifts to 7.0. At<br>
> which point the community much shift to 8.0.<br>
><br>
> Mark<br>
><br>
><br>
</div></div>> _______________________________________________<br>
> rules-dev mailing list<br>
> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
><br>
_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</blockquote></div><br></div></div>