-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/02/11 15:07, Nick Coghlan wrote: > One useful thing I have personally gotten out of this discussion is to > identify the core reason I feel backporting is the "right" way to > handle maintenance branches: it ensures that the *tests* that confirm > a bug has been fixed are always applied to the *latest* branch first. > This means that there should never be regressions of tested bug fixes, > even after a major version upgrade. When fixes and their associated > tests are applied to the oldest branch first, the only thing ensuring > the forward port isn't forgotten is manual review, thus opening the > door to regressions following a major version upgrade.
I am not sure I understand correctly. It is 4:15AM in Spain and I need to sleep badly. "Up-porting" CAN'T be forgotten because it is done "automagically" vía mercurial merges. That is the point... - -- 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/ iQCVAwUBTUtv4plgi5GaxT1NAQIoBQP+OATzNITrX9vsDLW3o01vH2VSbi1EN0+5 x+oYWyu8vkg+IenrF7TS3nfo+P72EC7AzqTCA5Nlhcc/HUsayrc0D73DVuUpeyac 5BsSDq2AbRPkQcMd8fhaAKxsWL5p4NIiYsqGO2Odhfu8ZBO+KKIdJZbsU2//cZAi hmr7/4tbiE4= =xoOv -----END PGP SIGNATURE----- _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
