Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/14/2015 08:14 AM, R. David Murray wrote: On Thu, 14 May 2015 07:15:34 -0700, Larry Hastings wrote: I'll start experimenting with the workflow(s) and will add documentation to the Dev Guide. The fun starts next weekend, By "next weekend" you mean "the weekend after this coming weekend",

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On Thu, 14 May 2015 07:15:34 -0700, Larry Hastings wrote: > I'll start experimenting with the workflow(s) and will add documentation > to the Dev Guide. > > The fun starts next weekend, By "next weekend" you mean "the weekend after this coming weekend", right? (These calendar idioms always con

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 10:04 AM, Larry Hastings wrote: What do you think? [...] Please cast your votes workflow 012 Larry Hastings-0.5 10.5 Brett Cannon 010 Nick Coghlan 010 Chris Angelico 000“in favor of [Workflow 1]” Ned Deily

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 05:19 PM, Nick Coghlan wrote: Workflow 0: -0 Workflow 1: +1 Workflow 2: +0 That's taking into account the clarification that the buildbots will be set up to track the 3.5.x branch after the beta is forked, and that Larry will also push the 3.5rcX repo to hg.python.org

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On Tue, May 12, 2015 at 8:04 PM, Larry Hastings wrote: > What do you think? My votes are as follows: > > Workflow 0: -0.5 > Workflow 1: +1 > Workflow 2: +0.5 > > > Please cast your votes, Workflow 0: -0 Workflow 1: +1 Workflow 2: +0 --Berker ___ pytho

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 11:18 AM, Jesus Cea wrote: 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

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 05:11 PM, Dirkjan Ochtman wrote: Couldn't you just keep this as a branch that you then keep rebasing (without unlinking the original branch)? It doesn't seem like something that needs a one-off script, to me. Probably. It's water under the bridge now--that all happened last Febr

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 13 May 2015 03:47, "Brett Cannon" wrote: > > > > On Tue, May 12, 2015 at 1:05 PM Larry Hastings wrote: >> >> [SNIP] >> >> >> What do you think? My votes are as follows: >>> >>> Workflow 0: -0.5 >>> Workflow 1: +1 >>> Workflow 2: +0.5 >> >> >> Please cast your votes, > > > Workflow 0: -0 > Wor

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On Tue, May 12, 2015 at 4:36 PM, Larry Hastings wrote: > BTW, this workload was exacerbated by my foolish desire to keep the revision > DAG nice and clean. So I was actually starting over from scratch and > redoing all the cherry-picking every couple of days, just so I could get all > the cherry-

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 11:21 AM, Ned Deily wrote: I like the idea of experimentally trying the push workflow but, if we are all doing our jobs right, there should be very few changes going in after rc1 so most committers won't need to push anything to the 3.5.0rc repo and, if for some reason they aren'

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On May 12, 2015, at 10:38 AM, Larry Hastings wrote: >It doesn't. Workflows 0 and 2 mean no public development of 3.6 until after >3.5.0 final ships, as per tradition. I still think it's a good idea to focus primarily on 3.5 while it's in the beta/rc period, but if you want to allow for landings

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

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? My votes: Workflow #0: -0 Workflow #1: +1 Workflow #2: +0 Would be great if we could host the branch for 3.5 ourselves instead of using BitBu

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On May 12, 2015, at 10:38, Larry Hastings wrote: > On 05/12/2015 10:23 AM, Ned Deily wrote: >> One possible issue with Workflow 1 is that there would need to be an >> additional set of buildbots (for 3.5, in addition to the existing 3.x (AKA >> "trunk"), 3.4, and 2.7 ones) for the period from be

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

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

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On Tue, May 12, 2015 at 1:05 PM Larry Hastings wrote: > [SNIP] > > What do you think? My votes are as follows: > > Workflow 0: -0.5 > Workflow 1: +1 > Workflow 2: +0.5 > > > Please cast your votes, > Workflow 0: -0 Workflow 1: +1 Workflow 2: +0 ___ p

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 10:23 AM, Ned Deily wrote: One possible issue with Workflow 1 is that there would need to be an additional set of buildbots (for 3.5, in addition to the existing 3.x (AKA "trunk"), 3.4, and 2.7 ones) for the period from beta 1 until at least 3.5.0 is released and, ideally, until 3

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On May 12, 2015, at 10:04, 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 request

[python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

Python 3.5 beta 1 is coming up soon. After beta is rc; after rc is 3.5.0 final. During the beta and rc periods the Python developer workflow changes a little--what sorts of checkins are permissible, and how to get something accepted and merged generally becomes more complicated. I was the