[Python-Dev] PEP 407: New release cycle and introducing long-term support versions (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Fri Jan 20 14:53:47 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 Fri, 20 Jan 2012 12:57:45 +0000 Paul Moore <p.f.moore at gmail.com> wrote:
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?
It sounds reasonable to me, although we probably wouldn't market it as a "trial run".
cheers
Antoine.
- 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 ]