A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2004-May/044986.html below:

[Python-Dev] pre-announcing 2.4

[Python-Dev] pre-announcing 2.4 [Python-Dev] pre-announcing 2.4Anthony Baxter anthony at interlink.com.au
Thu May 27 08:18:20 EDT 2004
Chermside, Michael wrote:
> I'd propose one change. Weaken the above statement. People will
> take that to mean that THEIR fix will be accepted ANYWHERE in
> the release process (including the day before the release). I'd
> suggest something more like this:
> 
>   Fixes are welcomed up through the alpha release, but as we
>   get closer to the release date we will be less and less
>   likely to accept patches that change behavior.

Good point, although this hides the point about the first beta
being the cut-off point for behaviour changes. How about

     Fixes are welcome through the release cycle, although after
     the first beta fixes that result in a change to behaviour
     will be much less likely to be accepted.

Once I have this message nailed down, I'll produce a similar
one for the bug fix releases.

-- 
Anthony Baxter     <anthony at interlink.com.au>
It's never too late to have a happy childhood.

More information about the Python-Dev mailing list

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