Larry Hastings <la...@hastings.org> added the comment: Marking an issue as "Release Blocker" is completely inappropriate for "I'd like to see this documentation change get into the next bugfix release."
Our Python Dev Guide discusses priority, here: https://devguide.python.org/triaging/#priority It says: "As a guideline, critical and above are usually reserved for crashes, serious regressions or breakage of very important APIs. Whether a bug is a release blocker for the current release schedule is decided by the release manager. Triagers may recommend this priority and should add the release manager to the nosy list. If needed, consult the release schedule and the release’s associated PEP for the release manager’s name." Please do not mark any bugs as "Release Blocker" in the future unless you are the release manager for that version. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33216> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
