FAQ
I've gone ahead and patched up a copy of the spec to resolve the version
issues I've been going on about (David, I wouldn't expect you to do the work
after you've just did all the work to mint the whole release).

The work can be found here for review.
http://github.com/schwern/cpan-meta/commits/master

I'm sure the wording around how to convert could be done better.

Here's what was done:

Clarifications:
--------------
AFAIK what I wrote exactly matches what version.pm does now. If it doesn't,
its a mistake.

* Version comparison has been documented.

* Version conversion has been documented.


Changes:
-------
* Downgraded the 999 dotted version limit to a "should".
Rationale: Its only for extreme backwards compat.

* Reduced the minimum number of integers in a dotted version to one.
Rationale: Neither v1 nor v1.2 are ambiguous.

* Three integers in a dotted version is now a "should".
Rationale: Its still a good idea.

* Changed the spec version to v3.0.0 to enable finer grained versioning
spec changes. See <http://semvar.org>.

* Changed the CPAN::Meta distribution version to v3.0.0.0 reflecting it
as the first release of the library representing v3.0.0 of the spec.
See https://rt.cpan.org/Ticket/Display.html?id=55718 for the patch
that allows vX.Y.Z Dist::Zilla versions.


--
101. I am not allowed to mount a bayonet on a crew-served weapon.
-- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
http://skippyslist.com/list/

Search Discussions

  • Zefram at Apr 21, 2010 at 3:28 pm

    Michael G Schwern wrote:
    * Downgraded the 999 dotted version limit to a "should".
    That's a pretty substantial change that shouldn't be made without the
    kind of detailed discussion that went into 2.0.
    * Reduced the minimum number of integers in a dotted version to one.
    Rationale: Neither v1 nor v1.2 are ambiguous.
    Dotted v1.2 is very different from fractional 1.2. Historically the "v"
    is not sufficient to distinguish them. The minimum of three segments
    in a dotted version has been devised precisely to avoid this ambiguity.

    On both of these points, spec version 2.0 is conforming to the "strict"
    syntax that has been carefully worked out for version.pm. The meta
    spec should continue to conform to the strict syntax unless there's an
    overwhelmingly good reason to deviate from it.

    -zefram

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcpan-workers @
categoriesperl
postedApr 21, '10 at 1:26p
activeApr 21, '10 at 3:28p
posts2
users2
websitecpan.org

2 users in discussion

Michael G Schwern: 1 post Zefram: 1 post

People

Translate

site design / logo © 2021 Grokbase