> What are the checkin policies to the sourceforge > CVS repository? > > Now that I have checkin rights (for the distutils), > I'm about to checkin new versions of the bdist_wininst > command. This is still under active development. > > Should CVS only contain complete, working versions? > Or are intermediate, nonworking versions allowed? > Will a warning be given here on python-dev just before > a new (beta) distribution is created? Please check in only working, tested code! There are lots of people (also outside the developers group) who do daily checkouts. If they get broken code, they'll scream hell! We publicize and discuss the release schedule pretty intensely here so you should have plenty of warning. --Guido van Rossum (home page: http://www.pythonlabs.com/~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