| |||||||||||||
Python ponders release numberingPython ponders release numberingPosted Feb 10, 2009 12:05 UTC (Tue) by rvfh (subscriber, #31018)Parent article: Python ponders release numbering
Call it 3.0.1 and do it quick, while not many people are using 3.0!
After all, the non-removal of cmp seems to be a bug, and thus needs a bug-fix...
Just my 0.02
(Log in to post comments)
Python ponders release numbering Posted Feb 10, 2009 15:38 UTC (Tue) by Wummel (subscriber, #7591) [Link]
I agree to a quick 3.0.1 release. Release early, release often. This scheme works well with a lot of free software.
Python ponders release numbering Posted Feb 10, 2009 18:09 UTC (Tue) by hppnq (guest, #14462) [Link] Release early, release often. But to discuss the removal of cmp() for more than a year, only to discover moments after the moment supreme of the 3.0 release, it was actually not removed, and then to discuss for two months and counting whether or not to fix this in release 3.1 or 3.0.1, that, well, that is something completely different.
Python ponders release numbering Posted Feb 12, 2009 19:51 UTC (Thu) by jordanb (guest, #45668) [Link]
It seems pretty absurd that they even got into this situation.
Why on earth didn't they take all the changes they'd decided to make, stick them in their bug tracker as 'critical', and only close them as the actual change was merged?
|
|||||||||||||