Meetings

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2007-11-14 11:35:58 →
Size: 978
Editor: 85-211-16-54
Comment:
← Revision 5 as of 2007-11-21 15:26:03 → ⇥
Size: 1560
Editor: 85-211-128-56
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:

=== Agenda - 2007-11-14 ===

 * Spec status - Lots of good discussions were held at UDS and good ideas were presented. These should now be formally integrated into the [:QATeam/Specs:specs]
 * Feedback on [:QATeam/HardySchedule:Hardy QA schedule]
 * Gutsy bug triage, looking for SRU candidtes
 * Managing [https://launchpad.net/ubuntu/gutsy/+nominations Gutsy] and [https://launchpad.net/ubuntu/dapper/+nominations Dapper] SRU nominees - the responsibility for sorting and evaluating these should be shared between the QA and release teams
 * QA team weekly meeting times

Meeting logs and reports

Agenda - 2007-11-14

  • Spec status - Lots of good discussions were held at UDS and good ideas were presented. These should now be formally integrated into the [:QATeam/Specs:specs]

  • Feedback on [:QATeam/HardySchedule:Hardy QA schedule]

  • Gutsy bug triage, looking for SRU candidtes

  • Managing [https://launchpad.net/ubuntu/gutsy/+nominations Gutsy] and [https://launchpad.net/ubuntu/dapper/+nominations Dapper] SRU nominees - the responsibility for sorting and evaluating these should be shared between the QA and release teams

  • QA team weekly meeting times

Agenda - 2007-10-24

  • post-release bug status - what's the damage?
  • mobile platform test cases
  • testing plans for hardy
  • bug management plans for hardy
  • new resources (every week)

Agenda - 2007-10-03

  • [:QATeam/Meetings/OsloSprint:Report] from the testing mini-sprint in Oslo

  • Selecting topics for UDS
  • Release Candidate next week - where are we on bugs?
  • QA team wiki pages
    • Should this one be merged with UbuntuQA?
    • How can we make the connections between the teams less confusing?
  • Agree upon a method for communicating high profile or well known bug reports amongst each other. It should be something that developers can add bug reports that they are working on too.
    • The bugsquad mailing list might be a good idea so other triagers see it to, the mailing list reports could then be added to a wiki page or vice versa

QATeam/Meetings (last edited 2013-08-12 22:21:05 by adsl-74-179-116-182)