Re: Meta v2 missing information on how to compare versions

David Golden wrote:
> Versions going forward will be integers so we can use the fractional 
> part for library release versioning.

I know, we could use one of those fancy dotted version numbers everyone's been 
talking about!

(What does the 101091 part of 2.101091 mean anyway?)

For important things like specifications I've come round to the Semantic 
Versioning way of doing it.  http://semver.org/  X increments on an 
incompatible change, Y on a new feature, Z on everything else.  This allows 
one to make minor changes and clarifications to the spec look different from 
incompatible OMGYOUDBETTERUPGRADE changes.  It frees you to make minor 
releases without causing everyone downstream to have to grovel through the 
change log to see if there was something significant.

Yeah, I know, irony me advocating X.Y.Z versions, but as long as we're stuck 
with them let's use them.

In that sense, adding a proper version spec would bring the spec up to v2.0.1 
or v2.1.0, either is arguable.  CPAN::Meta can then tack on as many extra dots 
as it wants.  v2.1.0.1 would be the second release of CPAN::Meta representing 
v2.1.0 of the spec.


-- 
But there's no sense crying over every mistake.
You just keep on trying till you run out of cake.
     -- Jonathan Coulton, "Still Alive"