Larry,
On 2015-05-12 1:04 PM, Larry Hastings wrote:
Workflow 1
==========
When I ship beta 1, we create the 3.5 branch. trunk become 3.6.
When I ship rc 1, the 3.5 branch becomes 3.5.1. I maintain a
publically visible repo /on bitbucket/ for 3.5.0, and we use bitbucket
"pull requests" for cherry-picks from 3.5.1 into 3.5.0.
This gives us a pilot project to try out a web GUI for merging. It
makes my workflow easier, as I can push a button to accept
cherry-picks. (If they don't apply cleanly I can tell the author to
go fix the conflict and resubmit it.) The downside: it requires core
devs to have and use bitbucket accounts.
This makes a lot of sense. +1.
Yury
_______________________________________________
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
