5.2.0 release plan

[AA-Turner]

I intend to release Sphinx 5.2.0 tomorrow (Saturday), 24/09/22.

Issues marked against 5.2.0: https://github.com/sphinx-doc/sphinx/milestone/130

Please alert me to any PRs/issues that should be included in 5.2.0.

A

[mgeier]

Can you please include #10692 in the release?

[jfbu]

@AA-Turner somehow I got not pinged from this issue creation (I do not watch all issue creations by default) so it is probably too late to consider merge of #10759. I did merge 5.x into it, so it is merge ready. Now, @tk0miya did not have time to review it so we can indeed delay to next one.

[AA-Turner]

Sphinx 5.2.0 has been released, thanks to all for your support and contributions.

A

[eandersson]

Is it intended that two versions were released?

5.2.0
5.2.0.post0

[AA-Turner]

Yes, see #10714 (comment)

A

[rkdarst]

FYI, the .post0 has caused a breakage in sphinx_rtd_theme, because it assumes that the sphinx version number has only three components separated by . (a, b, c = version.split('.')):

• issue: ValueError: too many values to unpack (expected 3) readthedocs/sphinx_rtd_theme#1343
• fixing PR: Support Sphinx post-releases readthedocs/sphinx_rtd_theme#1344

This is a problem in sphinx_rtd_theme, not sphinx (since .post0 is a documented version number). But, sphinx_rtd_theme is very commonly used and releases slowly, so there will probably be many projects needing to work around this.

If sphinx_rtd_theme doesn't release soon, the best "solution" is probably waiting for Sphinx to release again.

This is my personal workaround, which seems like it is being used by others as well:

sphinx!=5.2.0.post0    # remove after next release

[AA-Turner]

Sphinx 5.2.1 has been released.

A

[rkdarst]

Thank you! (on behalf of many sphinx users)
This, but also all of your general work on Sphinx.