Eli Bendersky eliben at gmail.com
Sat Mar 12 08:32:50 CET 2011

• Previous message: [Python-Dev] Suggest reverting today's checkin (recursive constant folding in the peephole optimizer)
• Next message: [Python-Dev] forward-porting from 3.1 to 3.2 to 3.3
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

The devguide's recommendation is to "forward-port" changes withing a major
release line, i.e. if I need something in all 3.[123], then start with 3.1
and forward-port (by "hg merge <branch>") to 3.2 and then 3.3

Just to clarify - does this mean that all changesets that are applied to 3.2
eventually get to 3.3 as well? Since we just do "hg merge 3.2" in the 3.3
clone, I guess this must be true. But then what happens if there's a change
in 3.2 that shouldn't get into 3.3? (say a bug fix for a feature that has
disappeared)?

Eli
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20110312/b463c9bc/attachment.html>

---

• Previous message: [Python-Dev] Suggest reverting today's checkin (recursive constant folding in the peephole optimizer)
• Next message: [Python-Dev] forward-porting from 3.1 to 3.2 to 3.3
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list