Skip to content

Conversation

@hugovk
Copy link
Member

@hugovk hugovk commented Sep 8, 2020

@gvanrossum
Copy link
Member

Wasn’t this omitted intentionally because it was a dud?

@hugovk
Copy link
Member Author

hugovk commented Sep 8, 2020

Python 3.5.9:

There were no new changes in version 3.5.9; 3.5.9 was released only because of a CDN caching problem, which resulted in some users downloading a prerelease version of the 3.5.8 .xz source tarball. Apart from the version number, 3.5.9 is identical to the proper 3.5.8 release.

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


Looking at the commits, I think 3.5.8 may have been removed by accident:

  • 3.5.8 final was added on its release date in 5b10add

  • Three days later, 3.5.8 final was left in place when 3.5.9 final was added on its release date in 28c92ac

  • Seven months later...

  • 3.5.9 was accidentally removed and put as a future release in 23585d7 (3.5.10 should have been added as a future release)

  • Two days later, the previous accident was cleaned up in 94a7f4c, but also removed 3.5.8

@ncoghlan
Copy link
Contributor

Perhaps it would make sense to add it back, but with a caveat in parentheses like "(replaced by 3.5.9 due to ambiguity with an incomplete pre-release build that escaped the release process)"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants