[Raymond Hettinger] > Is it appropriate to load improvements to the docs during this > week or is it hands-off for everything except new, critical bugs? In a perfect world, the only thing that would change between 2.3c1 and 2.3 final is the bits of code from which version numbers derive -- stability is the highest priority for a release candidate. It's possible that, e.g., the Cygwin woes will get pinned on the Python core before 2.3 final is released, and then if the fix(es) is(are) at all subtle, we'll have to do another release candidate. If people are eager to check in random improvements, it would be best to make a branch out of the rc1 tag (and random improvements could proceed on the head).
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