[Python-Dev] thinking about 2.7

Benjamin Peterson benjamin at python.org
Wed Sep 23 22:34:10 CEST 2009


2009/9/23 Brett Cannon <brett at python.org>:
> On Wed, Sep 23, 2009 at 07:35, Benjamin Peterson <benjamin at python.org> wrote:
>> Hi everyone,
>> I've started plotting the release of 2.7. I'd like to try for a final
>> release mid next summer. 3.2 should be released, if not at the same
>> time as 2.7, within a few weeks to avoid 2.x having features which 3.x
>> doesn't. If no one has problems with this, I will draft a schedule.
>>
>
> Yes. Does this mean you are volunteering to be the 3.2 release
> manager? Or simply prodding for volunteers? If it's the former are you
> at all worried about burn-out from doing two release so close together
> and being on the hook for two point releases at roughly the same time
> for about two years after?

While I certainly wouldn't mind doing only 2.7, I don't know how we
could preserve everyone's sanity and release them at about the same
time. Different RMs would have different times they can do releases,
so I would worry about there being a release in a slightly different
stage of a different branch every couple weeks.

As for burn out, I expected 2.7.x, as the last 2.x release, to be
different in that several people would do the maintenance releases
(perhaps on a 6 month schedule or so) for the 5 year period, so that
would leave me with just 3.2.x (and maybe another 3.1.x release).

...
>>
>> Additionally, I'm very apprehensive about doing any kind of release
>> without the buildbots running. Does anyone know when they might be up?
>
> I don't know the answer, but it might be "never". We used to do
> releases without them, so it's not impossible. Just means you have to
> really push the alphas, betas, and RCs.

What do you mean "push"?





-- 
Regards,
Benjamin


More information about the Python-Dev mailing list