On Fri, Feb 06, 2004 at 09:13:51PM -0800, Tim Wood wrote: > At 08:47 PM 02/06/04, Scott Beck wrote: > > > >To me a version number is nothing more than a loose representation of > >where the author thinks the code is in terms of stability and the only > >rule for versions is it must be changed from release to release. Just > >MHO. > > Good point. I'd like to hear from the POE-tentates their taxonomy of > release #s. That will help decide what to call the next one.
CPAN releases jump to the next 1/100. 0.01 = first cpan release 0.02 = second cpan release 0.03 = third cpan release The next release will be 0.29 unless it's decided to be something else. CVS releases are odd ten-thousandths after the most recent CPAN release. 0.0101 = cvs development after 0.01 0.0103 = cvs development after 0.0102 (see below) 0.0105 = cvs development after 0.0104 (see below) Release candidates and bugfixes are even ten-thousandths. 0.0102 = 0.02 rc 1 0.0104 = 0.02 rc 2 0.0106 = 0.02 rc 3 Private one-off releases are sometimes generated so someone with a bug or patch can test changes in their own environment. These are millionths releases. 0.010101 = private bugfix test snapshot 0.010103 = second bugfix snapshot (hope we got it this time) Various works planned and in progress are listed off http://poe.perl.org/?POE_RFCs -- Rocco Caputo - [EMAIL PROTECTED] - http://poe.perl.org/
