Home Original page

[Python-Dev] Devguide: Add a table summarizing status of Python branches

Brett Cannon brett at python.org
Wed Jan 20 15:20:02 EST 2016 
On Wed, 20 Jan 2016 at 10:40 Terry Reedy <tjreedy at udel.edu> wrote:

> On 1/20/2016 12:40 PM, Victor Stinner wrote:
> > Hi,
> >
> > I proposed a patch for the devguide to give the current status of all
> > Python branches: active, bugfix, security only, end-of-line, with
> > their end-of-life when applicable (past date or scheduled date)
> > http://bugs.python.org/issue26165
> >
> > What do you think? Does it look correct?
>
> I thought end-of-life was 5 years after initial release, not 5 years
> after last bugfix.


It is, which is why I requested the first release date be a column.


>   That would put eol for 3.4 in Feb 2019, I believe.
>
> > We will have to update this table each time that the status of a
> > branch change. Hopefully, it's not a common event, so it will not
> > require a lot of work for release managers :-)
>
> I believe there is some text describing current releases somewhere that
> also needs to be changed.  The release pep or scripts should have a
> reminder in the sections about the transitions.
>

PEP 101 would need a tweak to remind the RM to update the devguide.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20160120/5e5792de/attachment.html>
More information about the Python-Dev mailing list