classification
Title: devguide: table summarizing status of Python branches
Type: Stage:
Components: Devguide Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: ezio.melotti, koobs, larry, python-dev, vstinner, willingc
Priority: normal Keywords: patch

Created on 2016-01-20 17:36 by vstinner, last changed 2016-01-20 21:24 by vstinner. This issue is now closed.

Files
File name Uploaded Description Edit
branch_status.patch vstinner, 2016-01-20 17:36
Messages (6)
msg258696 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2016-01-20 17:36
A frequent question is to get the status of a Python branch: is it still maintained? when does the support stop?

Attached patch adds a short table giving the current status of Python branches between 2.6 and 3.6 (default).

I sorted branches by their status, nor by their value, to show immediatly that 2.7 is still at the top :-)

For the future end-of-life, I took the year of the last binary release and I added 5 years. Is that right?
msg258698 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2016-01-20 17:41
The table is inspired by http://docs.openstack.org/releases/ which only gives the status, not the past or scheduled end-of-life date.
msg258699 - (view) Author: Kubilay Kocak (koobs) (Python triager) Date: 2016-01-20 17:41
OH THANK YOU!

If possible, add Months or Quarter (Q1-4) for the EoL's, if those are defined, would be great.

We @ FreeBSD/Python would like to proactively (as early as possible) set DEPRECATED dates in our ports to ensure our users have ample time to upgrade to later versions, ideally in cadence with Python.
msg258717 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2016-01-20 21:16
New changeset 75b95ada261f by Victor Stinner in branch 'default':
Add a table "Status of Python branches" to the front page
https://hg.python.org/devguide/rev/75b95ada261f
msg258718 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2016-01-20 21:17
I pushed a first version of the table. It can be adjusted later if needed.
msg258719 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2016-01-20 21:24
> If possible, add Months or Quarter (Q1-4) for the EoL's, if those are defined, would be great.

I added the estimated *day* of the end-of-line. But the release manager is free to adjust it.

> We @ FreeBSD/Python would like to proactively (as early as possible) set DEPRECATED dates in our ports to ensure our users have ample time to upgrade to later versions, ideally in cadence with Python.

You may start to deprecate as soon as a branch switches to security only fixes?
History
Date User Action Args
2016-01-20 21:24:02vstinnersetmessages: + msg258719
2016-01-20 21:17:14vstinnersetstatus: open -> closed
resolution: fixed
messages: + msg258718
2016-01-20 21:16:51python-devsetnosy: + python-dev
messages: + msg258717
2016-01-20 17:41:57koobssetmessages: + msg258699
2016-01-20 17:41:54vstinnersetmessages: + msg258698
2016-01-20 17:36:22vstinnersetnosy: + larry, koobs
2016-01-20 17:36:12vstinnercreate