handling of bad-commit- tags needs improving
Bug #670792 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| qa-tagger |
Fix Released
|
High
|
Ursula Junque | ||
Bug Description
bugs with bad-commit-xxx should completely ignore the qa-* tags on the bug for the bad commit
Right now what seems to happen is that the deployment report stops if a bug is both
bad-commit-xxxx qa-needstesting
What should happen is that the report continues on until the rollback for xxx is found, and ignore the tags. Later (or earlier) commits for the same bug should respect the qa-* tags on it.
Tossing high on this - its affecting deployments.
| affects: | launchpad-foundations → qa-tagger |
| Changed in qa-tagger: | |
| status: | New → Incomplete |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 670792] Re: handling of bad-commit- tags needs improving | #1 |
Revision history for this message
| Ursula Junque (ursinha) wrote | #2 |
| Changed in qa-tagger: | |
| status: | Incomplete → In Progress |
| assignee: | nobody → Ursula Junque (ursinha) |
| Changed in qa-tagger: | |
| milestone: | none → 10.11 |
| Changed in qa-tagger: | |
| status: | In Progress → Fix Committed |
| Changed in qa-tagger: | |
| status: | Fix Committed → Fix Released |
| tags: | added: qa-ok |
To post a comment you must log in.
@Gary, what data do you need to complete this?