coordination #151822
Updated by JERiveraMoya 3 months ago
#### Motivation One area These are the two areas requested by upper management to take a look is look: _Soft failures_ : - Reduce the mitigation of soft failures. The goal is to reduce the ambiguity of this kind of failures ensuring we are not hiding any potential problem and cleanup is provided in a regular basis. See this confluence page for the general approach: https://confluence.suse.com/display/qasle/Soft-Fails+Mitigation In Yam squad we can apply something like this: - Recommended steps: - Understand the bugs, reproduce them and contact stakeholders. - Decide what to do with the bug, valid softfailure, remove it due it will not be fixed, update bug reference. - Care about reopening the bug for product in general maintenance or LTSS if the soft-failure occurred in a product that now doesn't meet those criteria or file a new bug if it happens in the new product under development._ **Avoid to just confirm that the problem is reproducible and focus more on taking some actions** , contacting stakeholders, creating new bugs and making some noise, and if nothing really works, last resource, it is to not test that test condition or workaround it without a soft-failure. _Change of focus at company level about some products_: - SLED - ~~HPC~~ will be an addon instead of a product. Additionally we could include here the clean-up of products with unsupported migration paths. #### Acceptance criteria **AC1**: Tackle soft failures to reduce the ambiguity/risk. ambiguity/risk **AC2**: Clean-up test coverage regarding product not on focus anymore #### Additional information - Bugs found during develpment of product that are now in maintenance might be ignored and we need to reopen it and link original bug. - Create a subtask in this epic for tackling each individual soft-failures ( _do not include more than 1 per ticket so we can use this as metric_ ). or related clusters of them. - Check also in development job groups.