How to categorize an issue as a release blocker?

openedx / wg-build-test-release

Open edX Build / Test / Release Working Group

24 stars 14 forks source link

How to categorize an issue as a release blocker? #292

Open mariajgrimaldi opened 1 year ago

mariajgrimaldi commented 1 year ago

Description

Usually, a release blocker is determined by the BTR team, but there is no guide to follow when categorizing them. Therefore, we should create a questionnaire that helps us decide when an issue is a release blocker to make the process more repeatable.

We can start the discussion here. Please, feel free to comment if you have any docs or insights on how to move forward.

regisb commented 1 year ago

The following are red flags:

normal user behaviour which has unexpected results
error 500
security issues or lack of support for a major component of the platform

mariajgrimaldi commented 12 months ago

Thanks @regisb, I added one more:

A release blocker is:

Normal user behaviour which has unexpected results
Error 500
Security issues or lack of support for a major component of the platform
Need for technology upgrades

I think for now that'd be enough. Thanks again

mariajgrimaldi commented 12 months ago

Some examples of what we've considered a release blocker: https://github.com/openedx/wg-build-test-release/issues?q=is%3Aissue+release+blocker

mariajgrimaldi commented 4 months ago

As an effort to align the release blocker criteria with the product prioritization, high-priority tests that fail are also considered release blockers. To sum up, a release blocker is:

High-priority tests that fail
Normal user behavior which has unexpected results. This should be discussed with product and the BTR-wg.
Error 5xx
Security issues or lack of support for a major component of the platform
Need for technology upgrades