[Python-Dev] When is it okay to cvs remove
? (original) (raw)
Guido van Rossum guido@python.org
Fri, 25 Apr 2003 01:24:45 -0400
- Previous message: [Python-Dev] When is it okay to ``cvs remove``?
- Next message: [Python-Dev] When is it okay to ``cvs remove``?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The policy about beta releases is (or should be) stricter. No new features, and perhaps no new tests unless they test for a bug that gets fixed. So in the beta cycle, patches are posted to SF just to store them there until after the release of Python 2.3.
I don't see much of a reason to be so strict about no new tests.
In the specific case, ask yourself what the cost would be if you produce a test failure under conditions that you consider obscure. Will enough people test the test before 2.3 is released? Does the new test suite behave differently enough from the old one to make false positives a possibility?
This is always a good set of questions to ask yourself.
--Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] When is it okay to ``cvs remove``?
- Next message: [Python-Dev] When is it okay to ``cvs remove``?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]