-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/02/11 10:54, Nick Coghlan wrote: > On Fri, Feb 4, 2011 at 1:17 PM, Jesus Cea <j...@jcea.es> wrote: >> "Up-porting" CAN'T be forgotten because it is done "automagically" vía >> mercurial merges. That is the point... > > So developer A checks in a fix on 2.7, then gets sidetracked before > forward porting it. > > When does it make it to 3.2 or the main development branch? > > Does everyone doing a forward merge from the maintenance branches run > the risk of being landed with the task of doing a bulk merge of any > forgotten forward ports before they can forward port the fix they're > actually trying to implement?
This is a social problem, not a tech one. In my opinion, the "owner" of a fix can not be considered "done" until the patch is merged everywhere. In fact, if all the branches were in the same repository (I do not advocate it), you can check it at push time. Failing to comply would be as bad as committing a patch leaving all buildbots in red, or unbuildable code. - -- 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/ iQCVAwUBTUvkVplgi5GaxT1NAQJlUAQAlX4V4H4kpSNn95fjNJVMgR6SwJzsYrUe SGeIuqMM5TALMxx/f9t5V1rE10JEV7nzNyKtdSnYDVom3RJL0fDNyvIsxrSzvTJM jJB+sTnMDI5cJ7m767B/Fz+xQ2Z7dpdjBJ3e/dZbqJmas4GkXWW3W5fjkU41Kvqu mqhpleBPpuo= =Y27E -----END PGP SIGNATURE----- _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
