-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/02/11 17:47, Barry Warsaw wrote: > This is one of the primary problems solved by a dvcs. You can *always* and > *easily* work on new features, publish them for comment and review by others, > make continual progress regardless of the release status of the official > branches, and easily track movement in those official branches.
That being true, I am interested in the buildbots. Publishing a private repository is not helpful, if you can't use the buildbots. I guess the best workflow would be for the Release Manager to create a clone, keeping the development repository open while the RM checks the clone and "cherry pick" changesets from the development branch if needed. When the release is complete, the clone can be tagged and merged back to the main development. So, nobody has to wait... > Pycon 2011 will mark the second anniversary of Guido's pronouncement. If we > do nothing else in Atlanta, can we *please* *please* *please* come away from > there with the conversion operationally completed? +inf!. - -- 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.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTUmTwplgi5GaxT1NAQIRbQP9FoUx5bcuwqiBVQczC2QBD7ad6ikVwN5e uf7ghaXkMltzUSgC5Bf3q+3yB/JVkfQ+gIK3TCvlQE+Kh7FlsKRd0MeKK62JDXwD U5YhKpX7CPGc14pM4+rEqaFuh5i/pbXNE8idNPd/kfk02CLt/+KKEoBwXmomm2cg Q/wUBlPrQZo= =M8ad -----END PGP SIGNATURE----- _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
