Add Severity Levels and response time
Signed-off-by: Luca Zizolfi luca.zizolfi@kalpa.it
Closed: oniro#589
Merge request reports
Activity
65 65 critical, normal, minor or low. 66 66 67 .. note:: 68 69 *Critical* severity bugs make a feature unusable, cause a major data loss or 70 hardware breakage. There is no workaround, or a complex one. 71 *Normal* severity bugs make a feature hard to use, but there is a workaround 72 (including another feature to use instead of the desired one). 73 *Minor* severity bugs cause a loss of non-critical feature (like missing or 74 incorrect logging). 75 *Low* severity bugs cause minor inconveniences (like a typo in the user 76 interface or in the documentation). 67 Severity Levels 68 ^^^^^^^^^^^^^^^^ 69 70 | **Critical - Response time: 3 working days.** -
3 working days for critical issue maybe too long from the users point of view. And way to long from the business point of view.
CC @dricci783
67 Severity Levels 68 ^^^^^^^^^^^^^^^^ 69 70 | **Critical - Response time: 3 working days.** 71 | Severity bugs make a feature unusable, cause a major data loss or 72 hardware breakage. There is no workaround, or a complex one. 73 | 74 | **Normal - Response time: 5 working days.** 75 | Severity bugs make a feature hard to use, but there is a workaround 76 (including another feature to use instead of the desired one). 77 | 78 | **Minor - Response time: 10 working days.** 79 | Severity bugs cause a loss of non-critical feature (like missing or 80 incorrect logging). 81 | 82 | **Low - Response time: Best effort.** -
"Best effort" is slippery slope [1] [2] We should use something like "commercially reasonable effort"
[1] https://definitions.uslegal.com/b/best-efforts/#:~:text=Best%20efforts%20is%20a%20contractual,ability%20to%20meet%20the%20goal. [2] https://www.lexology.com/library/detail.aspx?g=6a4c20dc-594d-4756-b710-7a2dc213e8c0
requested review from @dricci783, @aszpilko, @idlethread, and @alpianon
assigned to @lucazizolfi
This is your friendly STalE merge request FAmous bot remiNder (abbreviated as STEFAN).
This MR has been inactive for over a month now. Please update, close or comment why its still relevant even without activity within a week.
We are going to close stale issues after this reminder time frame has elapsed.
