Summary
Summary
- Bug Importance Guidelines
- Brian Murray (bdmurray) is sending an e-mail to the ubuntu-devel mailing list requesting a discussion about setting bug Importance on a per-package basis instead of on a per-distribution basis.
Iso Testing Bug report layout. While testing UME cgregan came up with a nice bug report template to write out reports. I am attempting to do the same thing for Iso testing. I think the polished our reports are the more the dev's will look to them. (As the QATeam I also feel we should lead the way hear too). Here is a Layout I've tried for the first time comments please. - davmor2
davmor2 is preparing a wiki page for collaboration on a template for the layout. See Testing/Bug-Report-Layout.
Usage of the term "Test Case" was brought up - see Testing/Cases.
Bugs in backport packages. Which should the policy with those be? It is clearly written that those packages are unsupported. -- AraPulido
- Backport packages are community supported.
- The policy is to open a task against the backports project and then close any Ubuntu task once it's verified to only be in -backports.
QA Liaison to Launchpad (LaserJock)
LaserJock has created a wiki page concerning this. See JordanMantha/QALiaison. This item has been moved to mailing list discussion.
FAUMachine for installation testing (LaserJock)
- FAUMachine was brought up as a potentially useful tool for automated testing.
- Items not on Agenda
A suggestion was made to improve inter-team linking (particularly on the wiki) between QA Team, BugSquad and Testing.
Jon Packard is adding an item to QATeam/RoadMap.
LaserJock has created a header for QA Team wiki subpages linking to BugSquad and Testing.
The QA Portal is now online at http://qa.ubuntu.com and should help with this.
QATeam/Meetings/20080730/Summary (last edited 2008-08-06 16:29:33 by localhost)