Activity log for bug #588908

Date Who What changed Old value New value Message
2010-06-02 20:42:24 Ursula Junque bug added bug
2010-06-02 20:42:56 Ursula Junque summary Add parsing capability to recognize the commit flags incr and no-qa Add parsing capability to recognize the commit flags [incr] and [no-qa]
2010-06-02 20:46:20 Ursula Junque summary Add parsing capability to recognize the commit flags [incr] and [no-qa] Add parsing capability to recognize the flags [incr] and [no-qa] in the PQM commit message
2010-06-07 13:34:57 Ursula Junque qa-tagger: status New Triaged
2010-06-07 13:35:09 Ursula Junque qa-tagger: assignee Ursula Junque (ursinha)
2010-06-07 13:35:13 Ursula Junque qa-tagger: assignee Ursula Junque (ursinha)
2010-06-07 13:35:23 Ursula Junque qa-tagger: importance Undecided High
2010-06-08 12:52:07 Ursula Junque qa-tagger: status Triaged In Progress
2010-06-08 12:52:09 Ursula Junque qa-tagger: milestone 10.06
2010-06-08 12:52:22 Ursula Junque qa-tagger: assignee Ursula Junque (ursinha)
2010-06-08 13:29:50 Ursula Junque tags orphaned-branches
2010-06-09 01:24:21 Ursula Junque description We're adopting two new flags in the PQM commit message: [incr] and [no-qa]. [incr]: This means that the commit is part of a larger goal, like a big feature or complicated fix. We shouldn't mark the bugs as Fix Committed, only add a message saying a commit is part of its fix. Also, in this case, we should check if there are bugs related and if not, send out emails. That's another bug I have to file. [no-qa]: This means we don't have to care about that commit, because it's something we don't need to QA. When finding this flag and a bug number, we should add it the tag "qa-untestable" tag. This needs to be implemented. We're adopting two new flags in the PQM commit message: [incr] and [no-qa]. [incr]: This means that the commit is part of a larger goal, like a big feature or complicated fix. We shouldn't mark the bugs as Fix Committed, only add a message saying a commit is part of its fix. Also, in this case, we should check if there are bugs related and if not, send out emails. That's another bug I have to file. [no-qa]: This means we don't have to care about that commit, because it's something we don't need to QA. When finding this flag and a bug number, we should add it the tag "qa-untestable" tag. This needs to be implemented: [no-qa] + [bug=...] : bug is marked as qa-untestable, not qa-needstesting [no-qa] : branch is OK to be an orphan (no bug) [incr] + [bug=...] : we do not add a tag to the bug or change its state (and, later, note that branch is an incremental change for a QA report) [bug=...] : bug is marked as qa-needstesting, as now.
2010-06-17 14:04:27 Ursula Junque qa-tagger: status In Progress Fix Committed
2010-06-17 15:38:58 Ursula Junque tags orphaned-branches orphaned-branches qa-needstesting
2010-06-18 01:11:57 Ursula Junque tags orphaned-branches qa-needstesting orphaned-branches qa-ok
2010-06-18 01:12:01 Ursula Junque qa-tagger: status Fix Committed Fix Released