RetroSearch Browse

Wed Jan 20 12:53:33 EST 2016 · https://mail.python.org/pipermail/python-dev/2016-January/142816.html

On Wed, 20 Jan 2016 at 09:41 Victor Stinner <victor.stinner at gmail.com>
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 would update it have a "first release" date column and also the projected
EOL for Python 3.5. Otherwise LGTM.

-Brett

>
> 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 :-)
>
> Victor
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/brett%40python.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20160120/3c56d0ea/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2016-January/142816.html below:

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