Meetings
Meeting logs and reports
["/OsloSprint"]
Agenda - 2007-11-28
- UDS activity report - I (heno) should write a summary of the QA sessions at UDS (but I wasn't there) Could those who were please send me 2-3 lines on the main results in QA from UDS?
Status of https://launchpad.net/ubuntu/gutsy/+nominations - heno
Specs approved for Hardy: https://wiki.ubuntu.com/QATeam/Specs
- Alpha 1 ISO testing - There is no freeze this time, but the key images should get a basic sanity test (basically check that they boot)
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