?
avatar brianteeman
brianteeman
17 Jun 2020

Problem identified

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

Proposed solution

Establish a set of criteria to be used.

Open questions

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)

avatar brianteeman brianteeman - open - 17 Jun 2020
avatar joomla-cms-bot joomla-cms-bot - change - 17 Jun 2020
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 17 Jun 2020
avatar brianteeman brianteeman - change - 17 Jun 2020
The description was changed
avatar brianteeman brianteeman - edited - 17 Jun 2020
avatar richard67
richard67 - comment - 17 Jun 2020

Ping @wilsonge .

avatar infograf768
infograf768 - comment - 18 Jun 2020

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.

avatar brianteeman
brianteeman - comment - 18 Jun 2020

None of them have made joomla unusable

avatar jwaisner jwaisner - change - 28 Jun 2020
Status New Discussion
avatar brianteeman brianteeman - change - 31 Jul 2020
Status Discussion Closed
Closed_Date 0000-00-00 00:00:00 2020-07-31 19:52:20
Closed_By brianteeman
avatar brianteeman
brianteeman - comment - 31 Jul 2020

Closed due to lack of response - guess no one is interested

avatar brianteeman brianteeman - close - 31 Jul 2020

Add a Comment

Login with GitHub to post a comment