Clarify revert / followup workflow for regressions, including subscribers

Created on 13 January 2017, over 8 years ago
Updated 26 March 2025, about 2 months ago

Since #66806: Don't let regular users re-open closed issues , issues can not be reopened by mere mortal users. Which is a good thing.

But some documented guidance how regressions should be handled, could help.
Example: there was quite some confusion how to handle a regression in #2828620: Regression: View pane rendering misuses and floods cache

So, technically speaking, this is a documentation bug as followup from #66806: Don't let regular users re-open closed issues .

Also: in ye olde days, when reopening an issue as of a regression, all subscribers were notified, which was a good thing. This is not the case anymore.

So, technically speaking, this is a feature regression as followup from #66806: Don't let regular users re-open closed issues .

(Feel free to separate these issues, i felt like starting with both and sorting this out might be better at first.)

📌 Task
Status

Postponed: needs info

Component

Missing documentation

Created by

🇩🇪Germany geek-merlin Freiburg, Germany

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024