A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-April/022620.html below:

[Python-Dev] Re: Stability and change

[Python-Dev] Re: Stability and changeAlex Martelli aleax@aleax.it
Mon, 8 Apr 2002 19:41:27 +0200
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




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4