Larry, could you comment about the impact in the buildbots?. I suppose
option #1 could allows us to test both 3.5 and 3.6 changes. Would you
confirm this?
Workflow #1 gets us automatic buildbot testing for the 3.5 branch
(betas and 3.5.1) and trunk (3.6). It doesn't get us testing of the
3.5.0 release candidates automatically, because those would be
hosted at bitbucket. However: hg.python.org allows creating
"server-side clones" which can manually run tests against the
buildbots. So if I create a server-side clone, then push the
release candidate branch there, I can kick off buildbot tests. Who
knows, maybe I'd even automate that process.