[core-workflow] Questions about the proposed workflows

[Barry Warsaw]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20151201/541d4bd9/attachment.sig>