[Python-Dev] Re: Stability and change (original) (raw)
Andrew Kuchling akuchlin@mems-exchange.org
Mon, 8 Apr 2002 12:39:03 -0400
- Previous message: [Python-Dev] Re: Stability and change
- Next message: [Python-Dev] Re: Stability and change
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Apr 08, 2002 at 12:30:10PM -0400, Guido van Rossum wrote:
Cheap shots aside, another possibility would be to simply start every minor (2.x) release off as unstable, releasing frequent experimental micro (2.x.y) releases as a substitute for alpha/beta releases, and then at some point declare it stable.
I like this approach because it matches what the community seems to actually be doing: the latest release is "experimental" until told otherwise. (Though who decides when it stops being experimental? Everyone here on python-dev thought 2.2 was OK, and I use 2.2 every day without pain, so I don't really know what people are complaining about.)
--amk (www.amk.ca) ... like a bull in a barber shop. -- The Doctor, in "Time and the Rani"
- Previous message: [Python-Dev] Re: Stability and change
- Next message: [Python-Dev] Re: Stability and change
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]