Python 2.7.15 release notes are not available

[mhsmith]

Python 2.7.15 was released yesterday. However, the release notes link on the download page doesn't go anywhere.

I see the 2.7 branch has changed the way they maintain their release notes file, so that's probably related.

[pradyunsg]

https://www.python.org/downloads/release/python-2715/

I was able to reach the above link after a single click on the web page linked in OP.

[mhsmith]

Yes, but that page still doesn't contain the full release notes. Compare it to the Python 2.7.14 page, which contains a "Full changelog" link.

And the "Release notes" link on the top-level downloads page is still broken.

[pradyunsg]

Aha. I see what you mean. I misread. My bad.

Maybe @ned-deily has something to say here.

[ned-deily]

@benjaminp is the release manager for Python 2.7.x releases.

[pradyunsg]

Whoops. Sorry for the noise. :)

[brainwane]

@benjaminp Hi! I was trying to figure out whether 2.7.15 includes PEP 566 support (to resolve conda/conda-build#2897 (comment) ) and couldn't find the release notes for 2.7.15. Ought I look at a combination of https://github.com/python/cpython/blob/2.7/Misc/NEWS.d/2.7.15rc1.rst and https://github.com/python/cpython/blob/2.7/Misc/NEWS.d/2.7.15.rst ?

Also, I see someone on python-list has also requested that we link to the 2.7.15 release notes.

[benjaminp]

Yes, the changes in 2.7.15 are the union of 2.7.15 and 2.7.15rc1 notes.

…

On Sun, May 20, 2018, at 07:57, Sumana Harihareswara wrote: @benjaminp Hi! I was trying to figure out whether 2.7.15 includes PEP 566 support (to resolve conda/conda-build#2897 (comment) ) and couldn't find the release notes for 2.7.15. Ought I look at a combination of https://github.com/python/cpython/blob/2.7/Misc/NEWS.d/2.7.15rc1.rst and https://github.com/python/cpython/blob/2.7/Misc/NEWS.d/2.7.15.rst ? Also, I see [someone on python-list] (https://mail.python.org/pipermail/python-list/2018-May/732762.html) has also requested that we link to the 2.7.15 release notes. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #1252 (comment)

[dmiller-nmap]

Any plans to publish the release notes for 2.7.15?

[berkerpeksag]

The release notes for 2.7.15 is already published. I've just linked them from the download page: https://www.python.org/downloads/release/python-2715/ (so there is a "Full Changelog" link now)

I think switching to Blurb has introduced a regression here. I'd expect 2.7.15.rst list all changes between 2.7.14 and 2.7.15 (including 2.7.15rc1), not only changes between 2.7.15.rc1 and 2.7.15 final.

[ned-deily]

Putting a link to just 2.7.t5.rst isn't a good solution as you note it's incomplete. There were two relevant changes here. A long ways back, the Python 3 documentation build was enhanced to produce a nicely formatted html version of the branch's changelog. That enhancement and other changes to the overall docset format were not backported to 2.7. Then, with the introduction of blurb to Python 2.7 and 3.x, there is no longer a single version-controlled file that contains the entire changelog; in the past the 2.7.x release pages could just point to the repo copy of that file. The Python 3.x doc builds were changed to use blurb to produce the html-formatted changelog but no similar change was made for 2.7 since blurb was not designed to produce the kind of plaintext changelog like the old 2.7 NEWS files. So either the 2.7 docs could be enhanced to produce a similar html changelog, which is kind of a big deal since it affects any process that builds the 2.7 docs, or a plain text version of the changelog could be created possibly manually and stored somewhere where it could be served from python.org.

[berkerpeksag]

Putting a link to just 2.7.t5.rst isn't a good solution as you note it's incomplete.

Agreed, I've tweaked it a bit:

(Feel free to suggest better wording.)

We can probably don't do anything, and link release notes manually (like I just did) until 2020 :)

[larryhastings]

For Python 3, building the docs runs "blurb merge", which generates what's essentially the old Misc/NEWS file. This then gets rst2html-ified and finds its final destination as "changelog.html". Then when we cut the release we link to the appropriate anchor on the release page, e.g.:

https://docs.python.org/3/whatsnew/changelog.html#python-3-7-1-final

Rather than... whatever it is you're proposing, why don't we also do that for Python 2?