[Python-Dev] Backport troubles with mercurial (original) (raw)
Amaury Forgeot d'Arc amauryfa at gmail.com
Wed Dec 29 11:09:21 CET 2010
- Previous message: [Python-Dev] Backport troubles with mercurial
- Next message: [Python-Dev] Backport troubles with mercurial
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2010/12/29 Georg Brandl <g.brandl at gmx.net>:
What worries me more is the requirement to find the correct branch before I can even edit the file. How would you, Georg, deal with doc patches (typos, bad markup)? Finding the correct branch is not really hard. Â Bugfixes go to maintenance, features to trunk.
This works well indeed, provided there is only one maintenance branch.
You need to think about which category your change is right now too, when deciding what to backport/svnmerge.
No, today this decision can take place after the development, some tickets got reopened because a backport was needed.
-- Amaury Forgeot d'Arc
- Previous message: [Python-Dev] Backport troubles with mercurial
- Next message: [Python-Dev] Backport troubles with mercurial
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]