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

Showing content from https://mail.python.org/pipermail/python-dev/2000-October/009673.html below:

[Python-Dev] Release candidate followed by feature freeze?

• Previous message: [Python-Dev] Re: [medusa] select, signals, and "interrupted system call" (EINTR)
• Next message: [Python-Dev] Release candidate followed by feature freeze?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> I'd like to poll opinions about this (we haven't had a PythonLabs
> group meeting about this yet).

YES! I was hoping somebody would propose such a thing; I was quite
concerned that check-in procedures are still that liberate.

To report how similar projects operate: In gcc, a CVS release branch
is created at some point in time (usually months before the
release). When the code is declared frozen, all changes to the release
branch have to go through the release manager. After the release,
"important" changes to the mainline branch are manually propagated to
the release branch for subminor releases.

Regards,
Martin

• Previous message: [Python-Dev] Re: [medusa] select, signals, and "interrupted system call" (EINTR)
• Next message: [Python-Dev] Release candidate followed by feature freeze?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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