On Fri, Feb 18, 2011 at 7:56 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > For the 3.2 series, I think living with the ambiguity for another 6 > months or so (however long it is until 3.2.1 is released) is the > better choice. There are enough parts of the release process that > involve the version number that we *really* shouldn't be messing with > it during the RC phase.
And the number 1 reason I consider messing with the numbering to be a bad idea: >>> "3.2" >= "3.2.0" False >>> (3, 2) >= (3, 2, 0) False If we miss anything, it could easily lead to errors like the two above. I'll grant that it *shouldn't* be any different to what happens when the release version gets bumped to 3.2.1 in the first maintenance release, but I really don't trust "should" all that much in a release management context :) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
