[Python-Dev] [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!) (original) (raw)
Dirkjan Ochtman dirkjan at ochtman.nl
Wed May 13 02:11:44 CEST 2015
- Previous message (by thread): [Python-Dev] [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
- Next message (by thread): [Python-Dev] [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, May 12, 2015 at 4:36 PM, Larry Hastings <larry at hastings.org> 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-picked revisions in strict chronological order. By the end I had evolved a pretty elaborate guided-process automation script to do all the cherry-picking, which you can see here if you're curious:
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.
Cheers,
Dirkjan
- Previous message (by thread): [Python-Dev] [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
- Next message (by thread): [Python-Dev] [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]