-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/02/11 21:30, Barry Warsaw wrote: >> Just exactly the reverse of current workflow. > > And for good reason (IMO). It's often much less clear exactly how far back a > specific patch should be committed when it's first being developed. It makes > much more sense to me to fix a problem in the current development branch > first, and then determine if, how, and where the patch should be back ported.
While I do agree with your point, when I take over a bug I test all supported versions to see which ones are buggy. Now you can choose to patch the latest and backport, or to patch the oldest and up-port. It is a choice. Mercurial is designed for up-porting. In fact, "up-porting" is usually better, because you don't have to think if you must downport or not. Versión "n+1" is always a superset of versión "n". So you "up-port" *ALWAYS*, automatically (mostly) via merge. If you choose the backporting way, you must take a decision about what to backport, for every single changeset. And god forbids you forget something in the process... I agree you have a point when you write a new functionality for the latest version and LATER somebody decides that a particular changeset must be backported. Or a fix not planed for old versions is re-scheduled. Would be very nice if the HG cherrypick extension would be more clever. Of if mercurial would recognize that a patch is already manually committed in both lines, and cope with that gracefully when merging. I am sure we are not alone with these issues, and I hope somebody is actually doing something about it. - -- 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/ iQCVAwUBTUn4zZlgi5GaxT1NAQLitQP/cWcs8zuR/bsEkLLzM0BKLKnvt+U/5EI9 EGfqTz+SOkB9g6Yvrh35r5LcyXREQGJz9jtvOQFo+6L5UOlhpDWDwBiyFW37sdzi SVrnzsog63DqAOpGVrOqwSV+0/pwgl7Kst5z9w+i42PD/atZsq2z31ze2qWP4QNM nvoR2K8HSSc= =cQ6Z -----END PGP SIGNATURE----- _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
