coordination #151822
Updated by JERiveraMoya 5 months ago
#### Motivation Soft failures: - Reduce the ambiguity of this kind of failures ensuring we are not hiding any potential problem and cleanup is provided in a regular basis. - Requested by upper management. - Recommended steps: - **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. #### Acceptance criteria **AC1**: Understand the bugs, reproduce them and contact stakeholders - **AC2**: Decide what to do with the bug, valid softfailure, remove it due it will not be fixed, update bug reference. - Care **AC3**: _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. #### Acceptance criteria **AC1**: Tackle soft failures to reduce the 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 or related clusters of them. - Check also in development job groups.