-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On May 8, 2008, at 9:41 AM, Michael Urman wrote:
On Thu, May 8, 2008 at 8:20 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
Or aggressively back out any changes from freeze time to tag time.
If we
don't add the commit hook lock, I will be very strict about this
come the
betas.
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? This way
only the release manager need know or care about the branch, and
nobody else has to really modify his behavior. Then tag, move, and/or
delete the branch as desired.
The obvious stumbling blocks include buildbots not following the new
branch (this could be a blocker), and release scripts possibly needing
modifications if they contain direct svn url references.
I definitely think we'd want the buildbots to track the release
branches, and it's a bit of a pain to get the release scripts to deal
with the svn switches. Right now I think the freeze window is pretty
short (barring unforeseen networking snafus) that it's not worth it.
However, once the release process is smooth enough, maybe this little
freeze hiccup will be worth eliminating.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBSCMNEHEjvBPtnXfVAQIDogP+NVpyE7AhUS1Eerqv/N+ERTuKnmy/rSNQ
wQhOlAxlvx/lPgm0Mi70C9cA60ogxwGE+nJPf0RQxN2bVfhE/+fvElRl9x7xuoo3
wAK6/zzItqMCP4bpaT8sbsqn4tPB4OCKr0eM/SgZMxrHZkHHZwLTVAw81h40Fmr3
A30V6JpZpdU=
=q3uu
-----END PGP SIGNATURE-----
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
