[Python-Dev] Re: Stability and change (original) (raw)
Alex Martelli aleax@aleax.it
Mon, 8 Apr 2002 19:41:27 +0200
- Previous message: [Python-Dev] Re: Stability and change
- Next message: [Python-Dev] Re: Stability and change
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Monday 08 April 2002 07:38 pm, Guido van Rossum wrote: ...
> It seems to me that duplicating (in your example) 2.3.8 to 2.4.0 > (and using 2.5.0 as the new baseline for further experimentation) > would be a very clear signal in this sense.
If the community likes the even/odd distinction enough. I've heard mixed feelings.
I'm neutral on the odd/even distinction -- all it has for it is that a number of people are used to it from Linux. But SOMEthing more remarkable that "up to 2.3.N experimental, 2.3.(N+1) and on stable" is needed -- a different name, a different major release, whatever. If we can come up with something better than parity of minor release number, I'll personally cheer... I just can't think of anything better right now. Comparison of microrelease with some arbitrary threshold changing by minor.major is worse, though -- not a clear signal at all.
Alex
- Previous message: [Python-Dev] Re: Stability and change
- Next message: [Python-Dev] Re: Stability and change
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]