There is considerable inconsistency in when the release blocker tag is added to an issue. This devalues the use of the term and steers contributors away from certain issues in favour of those with the release blocker tag
Establish a set of criteria to be used.
What should the criteria be? I would suggest basing them on the existing https://docs.joomla.org/Bug_and_Issue_Tracker_Priority
So for example a css error in a specific browser could never be a release blocker
But a delete button not working could be a release blocker (depending on where)
Labels |
Added:
?
|
So for example a css error in a specific browser could never be a release blocker
Disagree: we have many issues for example with Safari. We can't obviously release J4 if Safari is unusable.
None of them have made joomla unusable
Status | New | ⇒ | Discussion |
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-07-31 19:52:20 |
Closed_By | ⇒ | brianteeman |
Closed due to lack of response - guess no one is interested
Ping @wilsonge .