Am 17.03.14 14:52, schrieb Jesus Cea:

Do I need to do anything to create the 3.4 branch in the buildbots?.

As a slave operator, you don't need to do anything. As the master operator, you would have to edit the configuration file to add the branch.

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.

As the master operator, it would also be nice to slave operators if the 3.3 build directories get cleaned up, by targeting them to

http://hg.python.org/buildbot/empty/

once, and triggering a rebuild.

Regards, Martin

On lun., 2014-03-17 at 09:37 -0500, Zachary Ware wrote:

On Mon, Mar 17, 2014 at 9:16 AM, "Martin v. Löwis" martin@v.loewis.de wrote:

...

Am 17.03.14 14:52, schrieb Jesus Cea:

...

Do I need to do anything to create the 3.4 branch in the buildbots?.

As a slave operator, you don't need to do anything. As the master operator, you would have to edit the configuration file to add the branch.

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.

Since we still have a 3.2 configuration (for which most of the UNIX bots are broken), perhaps we should repurpose that configuration instead of 3.3.

That would be Georg's call, since he's the RM for both branches (AFAIR).

Regards

Antoine.

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