[Python-Dev] PEP 407: New release cycle and introducing long-term support versions

[Tim Golden]

On 20/01/2012 19:14, Georg Brandl wrote:
> Am 20.01.2012 00:54, schrieb "Martin v. Löwis":
>>> I can't help noticing that so far, worries about the workload came mostly from
>>> people who don't actually bear that load (this is no accusation!), while those
>>> that do are the proponents of the PEP...
>>
>> Ok, so let me add then that I'm worried about the additional work-load.
>>
>> I'm particularly worried about the coordination of vacation across the
>> three people that work on a release. It might well not be possible to
>> make any release for a period of two months, which, in a six-months
>> release cycle with two alphas and a beta, might mean that we (the
>> release people) would need to adjust our vacation plans with the release
>> schedule, or else step down (unless you would release the "normal"
>> feature releases as source-only releases).
>
> Thanks for the reminder, Martin.  Even with the current release schedule,
> I think that the load on you is too much, and we need a whole team of
> Windows release experts.  It's not really fair that the RM usually changes
> from release to release (at least every 2), and you have to do the same
> for everyone.
>
> It looks like we have one volunteer already; if we find another, I think
> one of them will also be not on vacation at most times :)


I'm certainly happy to help out there. Like everyone I'm
not always clear on my availability but the more people
who know what needs to be done, the better ISTM.

TJG