On Dec 01, 2015, at 06:58 PM, Donald Stufft wrote: >If the original PR was to the 3.4 branch, once you merge it you can, in the >web ui, create a new PR that merges 3.4 into 3.5, then 3.5 into 3.6. That’s >about the best that’s available right now.
I haven't had much luck with this, but it might be because my bug fixes go to devel first and then get selectively backported to the maintenance branches. So a merge in that direction pulls way to much stuff into the latter branch. Maybe it works better if you go in the other direction (essentially what the current hg workflow encourages), but the problem is that overwhelmingly contributions get proposed to the master, i.e. development, branch. Cheers, -Barry
pgpePcojes_ii.pgp
Description: OpenPGP digital signature
_______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
