Am 17.03.14 16:58, schrieb Jesus Cea: > On 17/03/14 15:16, "Martin v. Löwis" wrote: >> However, I would advise against doing so now, and delay the addition >> of the 3.4 branch until 3.3 is retired from bug fixing, and then >> repurpose all 3.3 configuration for 3.4. Otherwise, some slaves might >> run out of disk space. > > Are you actually talking about 3.2?. I am surprised that you propose to > delay 3.4 buildbots now that it is the "current" release. Doesn't make > sense to me.
No - the "current" branch is 3.5. The rationale for not creating buildbots for them right away is that 3.4 just had a release, and the next release might be a few month ahead, so enabling buildbots four weeks from now might still be early enough. > Why not drop 3.2 and do only 2.7, 3.3, 3.4 and default (future 3.5)?. I was actually unaware that there is a 3.2 configuration still; repurposing that is then fine with me. However, it might be a little bit more complicated, since the 3.2 configuration is not listed in https://www.python.org/dev/buildbot/ so you'll have to create a bunch of proxy, alias, redirect and whatnot configurations if you want to expose a fourth branch. Regards, Martin _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
