[Python-Dev] PEP 407: New release cycle and introducing long-term support versions (original) (raw)
Paul Moore p.f.moore at gmail.com
Fri Jan 20 13:57:45 CET 2012
- Previous message: [Python-Dev] PEP 407: New release cycle and introducing long-term support versions
- Next message: [Python-Dev] PEP 407: New release cycle and introducing long-term support versions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 20 January 2012 03:57, Brian Curtin <brian at python.org> wrote:
FWIW, it might well be that I can't be available for the 3.3 final release (I haven't finalized my vacation schedule yet for August). In the interest of not having Windows releases depend on one person, and having gone through building the installer myself (which I know is but one of the duties), I'm available to help should you need it.
One thought comes to mind - while we need a PEP to make a permanent change to the release schedule, would it be practical in any way to do a "trial run" of the process, and simply aim to release 3.4 about 6 months after 3.3? Based on the experiences gained from that, some of the discussions around this PEP could be supported (or not :-)) with more concrete information. If we can't do that, then that says something about the practicality of the proposal in itself...
The plan for 3.4 would need to be publicised well in advance, of course, but doing that as a one-off exercise might well be viable.
Paul.
PS I have no view on whether the proposal is a good idea or a bad idea from a RM point of view. That's entirely up to the people who do the work to decide, in my opinion.
- Previous message: [Python-Dev] PEP 407: New release cycle and introducing long-term support versions
- Next message: [Python-Dev] PEP 407: New release cycle and introducing long-term support versions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]