>From a non-perl-centric viewpoint, the vast majority of projects I work with nowadays abide by the semantic versioning concept (your v4) :
http://semver.org/ You lose the version's value as an actual number, but you gain more standard readability as to what the version means, which is something that I consider more valuable. -- Jarrod Overson On Thu, May 31, 2012 at 1:31 AM, Shlomi Fish <shlo...@shlomifish.org> wrote: > Hi all, > > earlier today I uploaded XML-LibXML-1.99 and since the 1.* releases had two > trailing digits, the next version will be past 2. This is a good to switch > to a > better versioning scheme, with more digits after the first dot, which will > give > us more air to breath. > > I'm asking you what the advantages and disadvantages of the following > schemes: > > 1. "2.xxyy" - "xx" are the major/new-feature versions, while "yy" are for > bug > fixes/maintenance versions. > > 2. "2.xxxyyy" - same as before only with three digits each. > > 3. "2.xxyyy" - same as before only a hybrid approach that will give a zero > in > the middle in case there are less than 100 maintenance versions. > > 4. "2.x.y" - I use this for my open source C projects and some of my CPAN > modules and perl 5 and Parrot use it as well. Is it well supported with the > CPAN toolchain? > > What do you recommend? > > Regards, > > Shlomi Fish > > -- > ----------------------------------------------------------------- > Shlomi Fish http://www.shlomifish.org/ > Parody of "The Fountainhead" - http://shlom.in/towtf > > He who reinvents the wheel, will understand much better how a wheel works. > > Please reply to list if it's a mailing list post - http://shlom.in/reply . >
