[issue25296] Simple End-of-life guide covering all unsupported versions

Mariatta Wijaya added the comment: This is not being tracked in: https://github.com/python/pythondotorg/issues/1302 -- nosy: +Mariatta ___ Python tracker ___

[issue25296] Simple End-of-life guide covering all unsupported versions

Andreas Lutro added the comment: 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

[issue25296] Simple End-of-life guide covering all unsupported versions

Changes by Berker Peksag : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue25296] Simple End-of-life guide covering all unsupported versions

Nick Coghlan added the comment: Adding Georg directly to the nosy, as I think this kind of structural question falls under his domain as the docs lead :) -- nosy: +georg.brandl ___ Python tracker

[issue25296] Simple End-of-life guide covering all unsupported versions

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list

[issue25296] Simple End-of-life guide covering all unsupported versions

STINNER Victor added the comment: Davey Shafik added the comment: > We (PHP) also have a more visual guide at > http://php.net/supported-versions.php which updates dynamically to show the > current status. Great job! It's much easier to see the status with the summary in a single picture.

[issue25296] Simple End-of-life guide covering all unsupported versions

Ezio Melotti added the comment: 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. --

[issue25296] Simple End-of-life guide covering all unsupported versions

Davey Shafik added the comment: 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

[issue25296] Simple End-of-life guide covering all unsupported versions

R. David Murray added the comment: 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

[issue25296] Simple End-of-life guide covering all unsupported versions

Georg Brandl added the comment: It should also be linked from the downloads page. -- ___ Python tracker ___

[issue25296] Simple End-of-life guide covering all unsupported versions

Georg Brandl added the comment: > It seems to me a link to this version independent info could logically appear > on the docs front page. Yes, that sounds good. I do like the PHP graph of versions too... -- ___ Python tracker

[issue25296] Simple End-of-life guide covering all unsupported versions

Carol Willing added the comment: And that would be EOL (end of life) not EOF. More coffee please... -- ___ Python tracker ___

[issue25296] Simple End-of-life guide covering all unsupported versions

Carol Willing added the comment: +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

[issue25296] Simple End-of-life guide covering all unsupported versions

STINNER Victor added the comment: 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

[issue25296] Simple End-of-life guide covering all unsupported versions

Nick Coghlan added the comment: 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:

[issue25296] Simple End-of-life guide covering all unsupported versions

Nick Coghlan added the comment: Items to capture for each unsupported or security fix only release series: * date & version of last binary release (maintenance -> security fix only transition) * date & version of last source-only security release (commercial redistributors are on their own

[issue25296] Simple End-of-life guide covering all unsupported versions

Ezio Melotti added the comment: > - the main docs are version specific, while this kind of page > should be version independent 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