Jeff Ramsdale wrote:
So technically Jonathan brought this up, not me, but I think it
deserves its own thread... :-)
We need to establish our versioning system. AR2 doesn't make any sense
to me, nor, more importantly, to Maven. Can we establish that our next
release is 2.2.0?
-jeff
+1 for 2.2.0
How about the following convention:
Major.Minor.Point
-Point Release, no API changes, bug fixes, internal implementation
refactoring only.
-Minor Release, Expanded API for existing packages, new utility
packages, no breaking of API backward (compile time) compatibility.
Bugfixes, reimplementation or refactoring of existing API functionality.
-Major Release, new Features, Packages & API, API Changes that Break
Source (compile time) compatibility but not binary (runtime) compatibility.
Cheers,
Peter.
