QA
Differences between revisions 1 and 2
|
⇤ ← Revision 1 as of 2008-05-16 14:04:00
Size: 341
Comment:
|
Size: 912
Comment: agendas
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 14: | Line 14: |
| === Session === | === Bug response times === |
| Line 16: | Line 16: |
| * Notes | Spec: https://blueprints.launchpad.net/foo ==== Agenda ==== * How can we measure it? * How can we improve it? * Display on per-package status page? * Larger picture: global bug volume ==== Notes ==== |
| Line 19: | Line 28: |
| === Bug escalation procedures === |
|
| Line 20: | Line 31: |
==== Agenda ==== * Case 1: World breaking regressions in stable or late devel version * Using the critical importance with an escalation bot * Case 2: Important bugs that need be made more prominent before release * Formal and informal escalation paths within the QA team ==== Notes ==== * Notes |
UDS Intrepid QA Report
[:UDS-Intrepid/Report:back to the reports index page]
Plans for 8.10
Place in this section bullet points of specific intended outcomes for the 8.10 development cycle.
- Outcome
- Outcome
Sessions
Bug response times
Spec: https://blueprints.launchpad.net/foo
Agenda
- How can we measure it?
- How can we improve it?
- Display on per-package status page?
- Larger picture: global bug volume
Notes
- Notes
Bug escalation procedures
Spec: https://blueprints.launchpad.net/foo
Agenda
- Case 1: World breaking regressions in stable or late devel version
- Using the critical importance with an escalation bot
- Case 2: Important bugs that need be made more prominent before release
- Formal and informal escalation paths within the QA team
Notes
- Notes
UDS-Intrepid/Report/QA (last edited 2008-08-06 16:15:30 by localhost)