Now that 2.1 is out, I've created a CVS branch for the Python 2.1.1 bugfix release. Its name is "release21-maint" (I had no choice in the name, I'm mimicking the name that Moshe chose for the 2.0.1 branch). Anything that should go into 2.1.1 ought to be checked into this branch as well as into the trunk. Let's tentatively shoot for a 2.1.1 release about a month for now. This ought to be a very conservative bugfix release; the key goal is stability of the 2.1 platform, not releasing features that missed the 2.1 deadline. Anything that smells of a feature or a new API (even if it is introduced to fix a design bug!) ought to go into the trunk, where it will be released as part of 2.2. I am aiming for a 2.2 release in October 2001. In the future, I'd like to create a branch for each release (alpha, beta or candidate). These branches will branch of the trunk just before the release is planned. That way, instead of declaring a checkin moratorium on the trunk, I can create a branch, and checkins on the trunk won't bother me (or whoever is the release manager). Thanks to all the last-minute bug reporters and fixers! --Guido van Rossum (home page: http://www.python.org/~guido/)
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