[Python-Dev] Rules of a beta release? (original) (raw)

Brett Cannon drifty@alum.berkeley.edu
Fri, 25 Apr 2003 17:07:34 -0700 (PDT)

[Guido van Rossum]

> > It's a good idea to document that urllib (currently!) never does > > newline translation. Given that URLs often point to binary files, > > that's probably a good idea! > > OK. I will patch the docs and the docstrings (and backport it as > necessary) after you raise the commit moratorium.

Consider it raised. Python 2.3b1 is officially released!

Wonderful!

> > > Thanks for fixing this, Guido. I think I am going to do a > > > self-imposed "no checkins within 24 hours of a planned release" > > > rule. > > > > Yeah, me too. :-) > > Perhaps this should be in the FAQ?

But then releases would be so boring! :-)

I think Raymond should add something about this in his next bit of "Hard Knocks"-type writing. =)

Now that we are officially in a beta release, I want to clarify what the ground rules are in terms of commits are. Obviously no new functionality such as new modules or built-ins. But what about small features? Specifically, since I have CVS commit I can finally apply my patch to regrtest.py to allow the use of a skips.txt file listing tests to skip (unless people don't want it anymore). Now that is a new feature, but it is minor and it is on an undocumented module (for now; I will get those docs done before 2.3 final is reached).

Is this reasonable to commit now? Anything else I should know so I don't run a muck in CVS? =)

-Brett