[Python-3000] [Python-checkins] r62848 - python/trunk/Objects/setobject.c

Fri May 9 10:11:08 CEST 2008

Michael Urman writes:
 > I know this way is fairly entrenched in the python release process,
 > but it sounds like it's using the tools incorrectly. In particular
 > with subversion is very easy (compared to cvs) to branch and to switch
 > branches locally. Why not create a new prerelease branch at the
 > beginning of freeze and only merge in the critical changes?
Well, speaking from experience:
 - some of the "critical changes" may only get committed on the
 release branch
 - something different from what's in the mainline may get committed
 on the release branch
 - the milestones are on a sideline, not on the mainline.
Getting these points right is essential to ensure that the beta
testers' work is actually relevant to the development process, that
bisection searches work correctly, etc.
 > only the release manager need know or care about the branch, and
 > nobody else has to really modify his behavior.
Behavior modification is the main point of having a release cycle.
Setting deadlines, changing the nature of the patches, bringing issues
to closure, etc. A release without a freeze is like a sentence
without a period, IMO.