-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/02/11 19:47, Antoine Pitrou wrote: > I don't think we are talking about branching after rc1 but after beta1, > so that the feature branch can continue receive non-bugfix patches. > That's quite many changesets to review.
A beta is like any other branch. The "canonical way" (TM) in mercurial is to write the patch for the "oldest" supported branch (in this case, the beta branch), and "up-port" it to the open devel repository. So, RM could say something like "beta branch is here. Commit there only things that MUST be in 3.3.0. For general development, commit to "py3k"". Anybody can merge from "beta" *TO* "py3k", for "up porting". The trick here is to patch the oldest supported version, and "up port" later, via mercurial merge. Just exactly the reverse of current workflow. - -- 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/ iQCVAwUBTUm8M5lgi5GaxT1NAQIgPAQAk4O26PQqlIi8S9S/3PVB09HinWTYJOhZ 0pD5ul6jkOO506ngZvjN6a652wsTq5CHscTnoyNHRRlq38Pn5Y6m4vZOYvIaH6P1 LGJ7b5bv97nrxSzHnfmMIyi7jGPbv7Jgv8otgov7UIJE3YeMtSjJrVZaG98Sv2rq Xdlv5DJwBb4= =f6/e -----END PGP SIGNATURE----- _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
