action #91674

SUSE QE Tools process proposal: Go further on regression fixing

Added by okurz 3 months ago. Updated 10 days ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:



Recently we have caused some regressions in production. Always we were quick to handle but still users were affected.
Whenever we encounter a regression we already try to find at least a second improvement, see .
Inspired by I think we can benefit from going further.


Fix the bug, fix the design, fix the process, explore further


#1 Updated by okurz 3 months ago

  • Description updated (diff)

#2 Updated by okurz 14 days ago

  • Status changed from New to Workable
  • Assignee set to okurz

During SUSE QE Tools estimation session we agreed that it's "workable" and I can take it. There were no clear objections as such but general support for the idea. I plan to propose checklist entries in our "concrete bugs" tickets and/or our "Definition of Done"

#3 Updated by okurz 14 days ago

  • Due date set to 2021-07-20
  • Status changed from Workable to Feedback

In I did

  • reference in "How we work on our backlog" where we already had an entry for regression handling
  • extend the Definition of Done to include "For regressions: A regression fix is provided, flaws in the design, monitoring, process have been considered"

In I extended with the suggestions for the defect template:

* <Fix the actual problem>
* <Consider fixing the design>
* <Consider fixing the team's process>
* <Consider to explore further>

asking the team if they are ok with that

#4 Updated by mkittler 14 days ago

Seems good to me.

#5 Updated by ilausuch 13 days ago

me too

#6 Updated by okurz 10 days ago

  • Status changed from Feedback to Resolved

With the received feedback we confirmed that the proposal was seen by at least a part of the team. Calling ticket "Resolved".

Also available in: Atom PDF