Tracking regressions across releases of Ubuntu
Currently the Ubuntu QA Team is using regression- tags to track bug reports. However, the tags aren't really release specific so there is no way to tell when a regression appeared and if it is a regression that has been carried forward between releases. This should be resolved before the quantity of regression- tagged bugs increases any further.
Blueprint information
- Status:
- Not started
- Approver:
- Marjo F. Mercado
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
<JFo>I wonder if it is currently possible for us to do this already using tags. We currently tag based on release, plus we do a pretty good job of identifying regressions and tagging them as such. It should be possible to do an advanced search based on release tag and regression- and gather bugs that contain All of those.
Work items:
[pvillavi] Document the policy on the HowToTriage page and create a Stock response: TODO
[pvillavi] Organize a bug day to review regression-
(being in a Triaged status and Lucid report) target the bugs to Lucid: TODO
