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

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