Hello everybody!
In the last QA meeting I stepped ahead and volunteered to organize
another QA Bug Day.
This week wasn't a good one, so I thought to schedule it to the next
Wednesday (March, 19th). If you think we need more time or something,
please let me know.
== Actions ==
Basically I'm proposing the follow actions for the QA Bug Day, nothing
much new here:
1st - Triage those 48 bugs in [1], this includes:
* Prioritize it;
* Mark any duplications;
* Add tags and any other project that can be related to the bug so
we can have the right eyes on it;
* Some cool extra stuff: comments with any suggestions, links to
logstash queries so we can have the real dimension of how critic the bug
in question is;
2nd - Assign yourself to some of the unassigned bugs if possible so we
can c(see [2])
3rd - Dedicate some time to review the 55 In Progress bugs (see [3])
AND/OR be in touch with the current assignee in case the bug hadn't
recent activity (see [4]) so we can put it back into triage steps.
And depending on how the things happen, I would suggest to not forget
Grenade which is also part of the QA Program and extend that effort into
it (see Grenade References with the same indexes of tempest's).
So that's pretty much it, I would like to hear any suggestion or opinion
that you guys may have.
== Tempest references ==
[1] -
https://bugs.launchpad.net/tempest/+bugs?field.searchtext=&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE
[2] -
https://bugs.launchpad.net/tempest/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on
[3] -
https://bugs.launchpad.net/tempest/+bugs?search=Search&field.status=In+Progress
[4] -
https://bugs.launchpad.net/tempest/+bugs?search=Search&field.status=In+Progress&orderby=date_last_updated
== Grenade references ==
[1] -
https://bugs.launchpad.net/grenade/+bugs?field.searchtext=&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE
[2] -
https://bugs.launchpad.net/grenade/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on
[3] -
https://bugs.launchpad.net/grenade/+bugs?search=Search&field.status=In+Progress
[4] -
https://bugs.launchpad.net/grenade/+bugs?search=Search&field.status=In+Progress&orderby=date_last_updated
--
mauro(sr)