Repository navigation
Simple End-of-life guide covering all unsupported versions #69483
Description
| BPO | 25296 |
|---|---|
| Nosy | @warsaw, @birkenfeld, @ncoghlan, @vstinner, @ezio-melotti, @bitdancer, @willingc, @Mariatta, @anlutro |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2016-01-25.01:55:22.013>
created_at = <Date 2015-10-02.05:27:49.173>
labels = ['type-feature', 'docs']
title = 'Simple End-of-life guide covering all unsupported versions'
updated_at = <Date 2018-09-15.11:42:56.018>
user = 'https://github.com/ncoghlan'bugs.python.org fields:
activity = <Date 2018-09-15.11:42:56.018>
actor = 'Mariatta'
assignee = 'docs@python'
closed = True
closed_date = <Date 2016-01-25.01:55:22.013>
closer = 'berker.peksag'
components = ['Documentation']
creation = <Date 2015-10-02.05:27:49.173>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 25296
keywords = []
message_count = 17.0
messages = ['252084', '252085', '252086', '252087', '252088', '252089', '252098', '252099', '252102', '252119', '252128', '252131', '252137', '252138', '258894', '325425', '325431']
nosy_count = 12.0
nosy_names = ['barry', 'georg.brandl', 'ncoghlan', 'vstinner', 'ezio.melotti', 'r.david.murray', 'docs@python', 'willingc', 'dshafik', 'glasnt', 'Mariatta', 'Andreas Lutro']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue25296'
versions = []
Activity
ncoghlan commentedon Oct 2, 2015
Katie McLaughlin recently pointed me at PHP's summary page for the End-of-Life dates for their various releases: http://php.net/eol.php
That seems like a useful thing to offer, but we unfortunately don't currently have a great place for this kind of documentation:
The "right" answer seems to be setting up a separate "docs" project on hg.python.org to use as the landing page for docs.python.org and for version independent information like this (the redirects already defined as part of PEP-430 should continue to handle unqualified deep links into the Python 2 docs).
I'm not sure how much reconfiguration work such a change would entail, though.
ncoghlan commentedon Oct 2, 2015
Adding Georg directly to the nosy, as I think this kind of structural question falls under his domain as the docs lead :)
vstinner commentedon Oct 2, 2015
We now putting the such page on python.org website, as PHP did?
I like the idea of being very explicit on EOL. It's a FAQ on mailing lists. Even for me, being involved in Python developments, it's not always easy to know the status of each branch. For example, I recently asked the question for Python 3.4 :-) The answer was that it will switch to security fixes only after the next 3.4.x release.
The EOL page must explain each stage of maintenance:
Python 2.6 reached its EOL or security fixes are still accepted?
I guess that Python <= 2.5, Python 3.0 and Python 3.1 are dead, right?
ncoghlan commentedon Oct 2, 2015
The branch status is captured in the release PEPs:
2.6 (& 3.0): https://www.python.org/dev/peps/pep-0361/
2.7: https://www.python.org/dev/peps/pep-0373/
3.1: https://www.python.org/dev/peps/pep-0375/
3.2: https://www.python.org/dev/peps/pep-0392/
3.3: https://www.python.org/dev/peps/pep-0398/
3.4: https://www.python.org/dev/peps/pep-0429/
3.5: https://www.python.org/dev/peps/pep-0478/
3.6: https://www.python.org/dev/peps/pep-0494/
The "devcycle" page in the developer guide captures the details of the difference phases: https://docs.python.org/devguide/devcycle.html
So perhaps the expedient near term solution would be to put this info on the devcycle page, and move it later?
ncoghlan commentedon Oct 2, 2015
Items to capture for each unsupported or security fix only release series:
ezio-melotti commentedon Oct 2, 2015
They could still be included in the main docs with a clear link at the top that says "For the most-recently updated schedule see d.p.o/3/eol.html.". Each version should still be correct -- it will just lack the eol dates for the newest releases.
The Unicode Consortium and the W3C do something similar (see e.g. http://www.unicode.org/reports/tr29/tr29-23.html and http://www.w3.org/TR/2014/WD-html5-20140617/).
Another option is to create a new repo where to put version-independent docs (e.g. the whatsnew, maybe even Misc/NEWS). It shouldn't be difficult to then include these pages in the main docs.
dshafik commentedon Oct 2, 2015
We (PHP) also have a more visual guide at http://php.net/supported-versions.php which updates dynamically to show the current status.
It shows the current status (EOL, Security only, Active) of releases from PHP 5.3, which is still the default for many LTS distros and still in common use.
vstinner commentedon Oct 2, 2015
Davey Shafik added the comment:
Great job! It's much easier to see the status with the summary in a
single picture.
ezio-melotti commentedon Oct 2, 2015
I like that, in fact I used the same format in my talk "The development process of Python": http://wolfprojects.altervista.org/talks/development-process-of-python-2011/ (slides 20/21).
The main problem is where to put all this though.
bitdancer commentedon Oct 2, 2015
It seems to me a link to this version independent info could logically appear on the docs front page. I think we ought to add the devguide there already, for instance. The 'Meta information' section seems perfectly appropriate...even though all the docs currently in there are maintained in the Docs directory, both 'about' and 'reporting bugs' are currently version-independent information.
birkenfeld commentedon Oct 2, 2015
Yes, that sounds good. I do like the PHP graph of versions too...
birkenfeld commentedon Oct 2, 2015
It should also be linked from the downloads page.
willingc commentedon Oct 2, 2015
+1 to adding the EOF info to the Docs front page and a link from the downloads page.
Also, +1 to David's suggestion to adding the devguide as well to the front page. In the future, it would be nice to add the devguide to the CPython repo instead of having it as a standalone. It would consolidate things in to one workflow instead of a different workflow for the devguide.
P.S. Ezio - nice slide deck content :)
willingc commentedon Oct 2, 2015
And that would be EOL (end of life) not EOF. More coffee please...
glasnt commentedon Jan 24, 2016
Hello!
I recently saw an announcement[0] about the adding of the lifecycle status right at the top of the devguide[1]. I believe this was added as part of bpo-26165[2]
Given this, can this issue be marked as Resolved?
0 - https://twitter.com/gvanrossum/status/690227337015590912
1 - https://docs.python.org/devguide/#status-of-python-branches
2 - https://bugs.python.org/issue26165
anlutro commentedon Sep 15, 2018
I see this has been closed, but the page on the devguide is still really hard to find. On the python IRC channel I often see questions about this and I always have a hard time finding the page with the correct information.
If I google "python version support" or "python version end of life" or "python version lifecycle" I don't arrive at that page. For some of these searches I even end up on a separate devcycle[1] page which only contains old versions of python. Compare that to PHP, where the official "supported versions" page is the top result no matter what I search for.
Nevermind the fact that the lifecycle of python versions is relevant to non-developers as well, making it un-intuitive to go to the devguide to find this information.
I really think this needs to be made part of python.org's main website, with some good SEO.
[1] https://devguide.python.org/devcycle/
Mariatta commentedon Sep 15, 2018
This is not being tracked in:
python/pythondotorg#1302
hugovk commentedon Dec 6, 2022
Update: a release cycle chart is now live at https://devguide.python.org/versions/
Re: issue python/docs-community#67 / PR python/devguide#988
vstinner commentedon Dec 6, 2022
Oh wow, that's amazing! Thank you very much!