This will allow on focusing a big road map for 3.0 maybe hitting some 2.1,2.2 on the road to progressively
introduce some changes and see how community reacts to them.
May I suggest that we use a clear notation for 'unstable' versions? With
the current one (ie, 2.0.0-Mx), people tend to think that it's stable
(stable <=> API is frozen).
What about using a N.5 for unstable versions, and N.0 for stable
versions? For instance,
2.5 will be unstable, and will be renamed 3.0-RC1 as soon as we have
frozen the API.
IMO, having N.1, N.2 etc is not necessarily a good idea. There is some
confusion between N.0 and N.1 versions, as N.0.x are already bug fixes.
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
