Greg Ward writes:
Now, there should also be semi-formal guidelines on what the different components of a version number *for modules* might mean:
Disagreement; I'd vote for mechanism, not policy. For example, recently I went through 3 pre-releases of xml-0.5; they could have been called 0.5a{1,2,3}. ILU's been at 2.0a{1-12}, and I have no idea if the developers ever plan to go to beta. Different developers use version numbers differently, in ways that are consistent in the large but inconsistent in small details. A side note: for the XML package, I think things are getting to the point that I want to create a fake build tree (the blib/ idea) in order to allow running the test suite without having to actually perform the installation. So, is there any implementation work that can be done? -- A.M. Kuchling http://starship.skyport.net/crew/amk/ Once you accept that the world is a giant computer run by white mice, all other movies fade into insignificance. -- Mutsumi Takahashi, on _The Hitch-hiker's Guide to the Galaxy_