Le jeu. 17 sept. 2020 à 11:57, Łukasz Langa firstname.lastname@example.org a écrit :
The 3.9 branch is now accepting changes for 3.9.1. To maximize stability, the final release will be cut from the v3.9.0rc2 tag. If you need the release manager to cherry-pick any critical fixes, mark issues as release blockers and/or add him as a reviewer on a critical backport PR on GitHub.
To see which changes are currently cherry-picked for inclusion in 3.9.0, look at the short-lived branch-v3.9.0 on GitHub.
I would like to get the following Sphinx fix: https://github.com/python/cpython/commit/c053402927d36f9f26160ded24999bf5109...
I closed the issue since it's fixed. Should I reopen it and mark the issue as release blocker?
Previously, building the Python documentation failed randomly. It prevented to merge some PRs.
We got issues in Fedora to build the documentation because of this bug:
Warning, treated as error: /builddir/build/BUILD/Python-3.9.0rc2/Doc/library/string.rst:311:duplicate token description of sign, other instance in library/functions make: Leaving directory '/builddir/build/BUILD/Python-3.9.0rc2/Doc'
Night gathers, and now my watch begins. It shall not end until my death.