[python-committers] [IMPORTANT] post 3.7.0b1 development now open
Mariatta Wijaya
mariatta.wijaya at gmail.com
Thu Feb 1 14:47:58 EST 2018
More information about the python-committers mailing list
Thu Feb 1 14:47:58 EST 2018
- Previous message (by thread): [python-committers] [IMPORTANT] post 3.7.0b1 development now open
- Next message (by thread): [python-committers] I created the "needs backport to 3.7" label on GitHub
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> > Should a patch for 3.6 be cherry-picked directly from master or from 3.7? > Does it matter? With hg, double forward merges had to be done linearly, as > from 3.6 to 3.7 and thence from 3.7 to 3.8 (master). cherry_picker.py and miss-islington will backport from master to newest branch first. So master -> 3.7, then master -> 3.6, and master -> 2.7. It does not backport from 3.7 -> 3.6. When doing it manually yourself, you should be able to backport from master -> 3.6 first and then master -> 3.7, it doesn't matter. Mariatta Wijaya -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20180201/cd3e0956/attachment.html>
- Previous message (by thread): [python-committers] [IMPORTANT] post 3.7.0b1 development now open
- Next message (by thread): [python-committers] I created the "needs backport to 3.7" label on GitHub
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list