Devguide: Add a table summarizing status of Python branches
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? 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
On Wed, 20 Jan 2016 at 09:41 Victor Stinner <victor.stinner@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@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org
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. 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. -- Terry Jan Reedy
On Wed, 20 Jan 2016 at 10:40 Terry Reedy <tjreedy@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.
I pushed my table, it will be online in a few hours (I don't know when the devguide is recompiled?): http://docs.python.org/devguide/triaging.html#generating-special-links-in-a-... By the way, it would be super cool to rebuild the PEPs with a post-commit hook server-side, rather than having to wait the crontab which requires to wait ~30 minutes (1h? I don't know exactly). 2016-01-20 21:20 GMT+01:00 Brett Cannon <brett@python.org>:
It is, which is why I requested the first release date be a column.
I added a Scheduled column with a link to the Release Schedule PEP of each version. I also added a column with the date of the first date. I added 5 years to estimate the end-of-line. I used the same month and same date, with a comment above explaining that the release manager is free to adujst the end-of-line date. Thanks for the feedback.
PEP 101 would need a tweak to remind the RM to update the devguide.
Can someone please mention this table in the PEP Victor
On Wed, 20 Jan 2016 at 13:22 Victor Stinner <victor.stinner@gmail.com> wrote:
I pushed my table, it will be online in a few hours (I don't know when the devguide is recompiled?):
http://docs.python.org/devguide/triaging.html#generating-special-links-in-a-...
By the way, it would be super cool to rebuild the PEPs with a post-commit hook server-side, rather than having to wait the crontab which requires to wait ~30 minutes (1h? I don't know exactly).
This is a proposed optional, future feature leading from moving to GitHub: https://www.python.org/dev/peps/pep-0512/#web-hooks-for-re-generating-web-co... -Brett
2016-01-20 23:01 GMT+01:00 Brett Cannon <brett@python.org>:
This is a proposed optional, future feature leading from moving to GitHub: https://www.python.org/dev/peps/pep-0512/#web-hooks-for-re-generating-web-co...
I'm using the free service ReadTheDocs.org and it's really impressive how fast it is to update the HTML page after a push. It's usually less than 10 seconds. Victor
On Wed, 20 Jan 2016 at 14:28 Victor Stinner <victor.stinner@gmail.com> wrote:
2016-01-20 23:01 GMT+01:00 Brett Cannon <brett@python.org>:
This is a proposed optional, future feature leading from moving to GitHub:
https://www.python.org/dev/peps/pep-0512/#web-hooks-for-re-generating-web-co...
I'm using the free service ReadTheDocs.org and it's really impressive how fast it is to update the HTML page after a push. It's usually less than 10 seconds.
I have no idea if the way our docs are built would work on readthedocs.org, but if it could then I would definitely vote to move our docs there and have the PSF make a regular donation for the service. But this is a discussion to have on core-workflow@ and not here.
2016-01-21 1:09 GMT+01:00 Brett Cannon <brett@python.org>:
On Wed, 20 Jan 2016 at 14:28 Victor Stinner <victor.stinner@gmail.com>
I'm using the free service ReadTheDocs.org and it's really impressive how fast it is to update the HTML page after a push. It's usually less than 10 seconds.
I have no idea if the way our docs are built would work on readthedocs.org, but if it could then I would definitely vote to move our docs there and have the PSF make a regular donation for the service.
Oh, I was talking about small documentations of personal projects. I didn't propose to move Python docs to readthedocs.org. I don't know if it makes sense. It's just to say that we can do better than 30 minutes of the current system :-) Victor
2016-01-20 22:22 GMT+01:00 Victor Stinner <victor.stinner@gmail.com>:
I pushed my table, it will be online in a few hours (I don't know when the devguide is recompiled?): http://docs.python.org/devguide/triaging.html#generating-special-links-in-a-...
Hum ok, it takes more than a few hours in fact. It's still not online 10 hours after my push :-/ https://docs.python.org/devguide/ Victor
It's live: https://docs.python.org/devguide/#status-of-python-branches On Wed, 20 Jan 2016 at 23:47 Victor Stinner <victor.stinner@gmail.com> wrote:
2016-01-20 22:22 GMT+01:00 Victor Stinner <victor.stinner@gmail.com>:
I pushed my table, it will be online in a few hours (I don't know when the devguide is recompiled?):
http://docs.python.org/devguide/triaging.html#generating-special-links-in-a-...
Hum ok, it takes more than a few hours in fact. It's still not online 10 hours after my push :-/ https://docs.python.org/devguide/
Victor _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org
Thanks Victor for doing this. I'm starting a campaign to tell people about it on Twitter. :-) On Thu, Jan 21, 2016 at 9:18 AM, Brett Cannon <brett@python.org> wrote:
It's live: https://docs.python.org/devguide/#status-of-python-branches
On Wed, 20 Jan 2016 at 23:47 Victor Stinner <victor.stinner@gmail.com> wrote:
2016-01-20 22:22 GMT+01:00 Victor Stinner <victor.stinner@gmail.com>:
I pushed my table, it will be online in a few hours (I don't know when the devguide is recompiled?):
http://docs.python.org/devguide/triaging.html#generating-special-links-in-a-...
Hum ok, it takes more than a few hours in fact. It's still not online 10 hours after my push :-/ https://docs.python.org/devguide/
Victor _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (python.org/~guido)
On 21 January 2016 at 17:18, Brett Cannon <brett@python.org> wrote:
It's live: https://docs.python.org/devguide/#status-of-python-branches
Nice :-) Minor nit, the status column says "end of life", but the text below the table uses the term "end of line" (as does the comment "Versions older than 2.6 reached their end-of-line". From my experience, "end of life" is the more common term. Paul
On 1/21/2016 10:42 AM, Paul Moore wrote:
On 21 January 2016 at 17:18, Brett Cannon <brett@python.org> wrote:
It's live: https://docs.python.org/devguide/#status-of-python-branches
Nice :-)
Minor nit, the status column says "end of life", but the text below the table uses the term "end of line" (as does the comment "Versions older than 2.6 reached their end-of-line". From my experience, "end of life" is the more common term.
I'd prefer end-of-support -- bet you can't count how many pre 2.5 installations are still live. Emile
Emile van Sebille writes:
I'd prefer end-of-support -- bet you can't count how many pre 2.5 installations are still live.
I see your point, but (having just been thinking about CLAs and Schneier's blog) have to suggest that software that has an explicit "security support" period and is in use after that ends isn't "live". It is "undead". Hope-the-admin-is-named-Alice-ly y'rs,
On 22 January 2016 at 07:27, Emile van Sebille <emile@fenx.com> wrote:
On 1/21/2016 10:42 AM, Paul Moore wrote:
On 21 January 2016 at 17:18, Brett Cannon <brett@python.org> wrote:
It's live: https://docs.python.org/devguide/#status-of-python-branches
Nice :-)
Minor nit, the status column says "end of life", but the text below the table uses the term "end of line" (as does the comment "Versions older than 2.6 reached their end-of-line". From my experience, "end of life" is the more common term.
I'd prefer end-of-support -- bet you can't count how many pre 2.5 installations are still live.
I can count the number of folks contributing changes to the upstream Python 2.5 branch: zero. Even if somebody offered a patch for it, we wouldn't accept it - that maintenance branch is dead, which is what the "End of Life" refers to. Folks are still free to run it (all past Python releases remain online, all the way back to 1.1), and downstreams may still offer support for it, but that's their call. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
2016-01-21 18:18 GMT+01:00 Brett Cannon <brett@python.org>:
It's live: https://docs.python.org/devguide/#status-of-python-branches
There is a very strange bug in this website. This URL shows the table: https://docs.python.org/devguide/ This URL doesn't show the table: https://docs.python.org/devguide/index.html Outdated version of the guide? This bug can be seen without a browser, using wget: $ wget -O- https://docs.python.org/devguide/ 2>&1|grep 'Python branches' <span id="branchstatus"></span><h2>Status of Python branches<(...) <li><a class="reference internal" href="#status-of-python-branches">Status of Python branches</a></li> $ wget -O- https://docs.python.org/devguide/index.html 2>&1|grep 'Python branches' <not found, empty output> Victor
On Fri, Jan 22, 2016 at 6:03 PM, Victor Stinner <victor.stinner@gmail.com> wrote:
2016-01-21 18:18 GMT+01:00 Brett Cannon <brett@python.org>:
It's live: https://docs.python.org/devguide/#status-of-python-branches
There is a very strange bug in this website.
This URL shows the table: https://docs.python.org/devguide/
This URL doesn't show the table: https://docs.python.org/devguide/index.html
Outdated version of the guide?
It looks like a cache issue. I purged the cache for /devguide/index.html: $ wget -O- https://docs.python.org/devguide/index.html 2>&1 | grep "Python branches" <span id="branchstatus"></span><h2>Status of Python branches<a class="headerlink" href="#status-of-python-branches" title="Permalink to this headline">¶</a></h2> <li><a class="reference internal" href="#status-of-python-branches">Status of Python branches</a></li> --Berker
participants (9)
-
Berker Peksağ -
Brett Cannon -
Emile van Sebille -
Guido van Rossum -
Nick Coghlan -
Paul Moore -
Stephen J. Turnbull -
Terry Reedy -
Victor Stinner