-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/14/2010 03:35 AM, Benjamin Peterson wrote: >> Mercurial, where are you?. This would be a non issue :) > > How so?
The release manager could clone the repository to getting it ready for release, while the main repository accepts new changesets. The point would be not stopping commits, ever. When done, the release manager could tag the release in his/her clone and push the changes to the main branch, like any other commit. If the release manager needs some patches for the main repository, he/she can cherrypick them manually or using a tool like http://mercurial.selenic.com/wiki/TransplantExtension . The devil is in the details, like how the release manager repository clone accesses buildbots, for instance. This is possible workflow. I don't know what is the actual plan, yet. - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBS5xPUZlgi5GaxT1NAQJ6zgP+MOYKeZqMnSHZYATJ2TFMb1mRW1IjjSg6 kdlpLwaLIEM6QKjs6gAJP4QNmIigH0l7gJlZkDaP+FpD90teAbGqJe5xNKyQeZLg xitTu2spFZu8pD2GSZ1GLSq917poOyntYsyLhZ/ICS1QiUPiQItvUIhP3AEociEy WxzRJIZmrMg= =HmlY -----END PGP SIGNATURE----- _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
