IdeaPool
|
⇤ ← Revision 1 as of 2008-07-21 02:33:59
Size: 1286
Comment: Initial page with Dev / Triager Training Day outline
|
Size: 1289
Comment: formating
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 14: | Line 14: |
| * Providing a list of "need-to-have" information for debugging a particular package (logs, traces, etc). * Communicating the severity of a bug via the Importance field in LP. * ... |
* Providing a list of "need-to-have" information for debugging a particular package (logs, traces, etc). * Communicating the severity of a bug via the Importance field in LP. * ... |
This page is meant to be a virtual whiteboard for members of the QATeam when brainstorming new ideas for the QA efforts of Ubuntu.
If you have any ideas, please feel free to discuss them on the [https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa mailing list] and the irc channel (#ubuntu-quality on Freenode).
Idea Pool
Ideas on this page are to be considered a 'work in progress' and not as official statements by the QATeam or any group member. Please feel free to add ideas below and make comments.
Dev / Triager Training Days
The purpose of one of these days (which could be rolled with an UbuntuHugDay) is to provide a space and time for developers to ask bug triagers questions on best practices.
The rationale for this is that many developers started doing their work before many new changes in the way triage happens in Ubuntu and Launchpad came about. What makes this different from a general "learn how to triage" event is that it is focused on helping developers, not triagers (specifically, but triagers are welcome to attend).
Some things to cover include:
- Providing a list of "need-to-have" information for debugging a particular package (logs, traces, etc).
- Communicating the severity of a bug via the Importance field in LP.
- ...
QATeam/IdeaPool (last edited 2012-12-21 09:42:43 by javier-lopez)