Bugs should be marked Fix Committed as soon as the fix reaches devel branches
Bug #540326 reported by
Ursula Junque
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| qa-tagger |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Today, the new qa tagging script only marks the bug as Fix Committed when the fix reaches a qa-able state, that is reaching staging or edge.
It would be more correct to have them marked as Fix Committed when the fix is committed in devel or db-devel, and then just add the qa-needstesting tag when it comes the time.
| Changed in lp-qa-tools: | |
| milestone: | none → 10.03 |
| assignee: | nobody → Ursula Junque (ursinha) |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in lp-qa-tools: | |
| milestone: | 10.03 → 10.04 |
| affects: | lp-qa-tools → qa-tagging |
| Changed in qa-tagging: | |
| milestone: | 10.04 → none |
| Changed in qa-tagger: | |
| status: | Triaged → Invalid |
| assignee: | Ursula Junque (ursinha) → nobody |
| status: | Invalid → Triaged |
| Changed in qa-tagger: | |
| importance: | High → Low |
To post a comment you must log in.
