Editing QA meeting
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
- | + | '''QA Meeting Agenda''' | |
- | Please place the things you wish to discuss at the QA meeting on | + | Please place the things you wish to discuss at the QA meeting on IRC below. |
- | ''' | + | '''Meeting details''' |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
* IRC: irc.freenode.org | * IRC: irc.freenode.org | ||
Line 18: | Line 9: | ||
* Time: Tuesday, November 10th, 14:30 UTC | * Time: Tuesday, November 10th, 14:30 UTC | ||
- | + | '''Agenda''' | |
* QA is good. | * QA is good. | ||
Line 29: | Line 20: | ||
* specific bug report should always be required to block a package from entering Extras. | * specific bug report should always be required to block a package from entering Extras. | ||
* Developer's karma and tester's karma should be incorporated so that a "developer with high karma would be able to push packages through the process faster, and a high rolling tester would be able keep bugs open and classified as critical in case of disagreement." | * Developer's karma and tester's karma should be incorporated so that a "developer with high karma would be able to push packages through the process faster, and a high rolling tester would be able keep bugs open and classified as critical in case of disagreement." | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- |
Learn more about Contributing to the wiki.