My recommendation is to use semantic versioning and stick with it: * x.y.z * z = bug fixes only * y = any new features or changes to existing features * x = any backward compatibility loss in APIs / usage of the product
With that said, whatever approach is used, let's make clear guidelines and stick with it. The biggest advantage of sticking with semantic versioning is it's wide-spread use in the industry, with maven, and in the open source community. For example, IIUC, maven will allow a dependency upgrade at the minor version level but not at the major version level (when there are two dependency chains leading to different versions of the same artifact). -- View this message in context: http://activemq.2283324.n4.nabble.com/HEADS-UP-Discussion-Artemis-Planning-a-release-soon-tp4700793p4701053.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
