[QA Community] Release Meeting 2012-06-08

[Nicholas Skaggs]

Part Deux, the non-abbreviated addition:

=== What was done engineering wise? ===
* During the planned week of pre-testing (which was announced late in
the week, and therefore only had ~3-4 days of pre-testing), 9 people ran
21 testcases and 11 bugs were reported. At least 4 bugs reported were
caught in time to be fixed on 6/04 in the initial alpha 1 builds.
Overall, the combined total number of daily testers prior to alpha one
was 14 with a total of 66 testcases and 18 bugs reported. Alpha two will
ensure the planned pre-week of testing, with a focus on more folks
running the daily iso and report issues before the milestone.
* During alpha 1, 37 people participated, giving us 100% mandatory test
coverage for the final iso spins for ubuntu desktop images. This is
quite a testament given the 11+? respins of alpha one! This represents
an excellent start on fulfilling the commitment to assure quality
throughout the release; and the 100% coverage is atypical to previous
alpha 1 releases. For a full report, please see
https://wiki.ubuntu.com/QATeam/ReleaseReports/QuantalAlpha1TestReport.
* The QATracker staging site contains the first call for testing
utilizing the qatracker. The goal is to enable better metrics tracking,
as well as consolidate feedback and make it easier for testers to test.
As of writing, interest expressed in using the kernel has been strong
(and seemingly installations), but results submitted are still lacking.

=== What's about to land that might impact the other teams and release
as a whole? ===

* Next week should have further feedback on utilizing the new qatracker
to conduct calls for testing
* Will be meeting with ubuntu flavors teams (and community) to discuss
QA best practices
* Will be reviewing alpha one process and results to help improve alpha
two -- happy to hear feedback on good/bad

=== Summary of bugs working on by team (reasonably reliable) ===

* N/A

=== Dependencies on other teams to make deliverables, blocking items,
release wide concerns? ===

* On-going dependency on the new qatracker codebase to release to
jump-start further manual testing, SRU testing, and calls for testing
* Community Unity testing process is still being finalized; needs to fit
into the new structure

Thanks,
Nicholas

On 06/08/2012 11:27 AM, Nicholas Skaggs wrote:
> === What was done engineering wise? === 
> * Alpha One ISO Testing (and release :-) )
> * Call for testing 12.10 kernel on 12.04
>
>  === What's about to land that might impact the other teams and release as a whole? ===
>
> * N/A
>
> === Summary of bugs working on by team (reasonably reliable) === 
>
> * N/A
>
> === Dependencies on other teams to make deliverables, blocking items, release wide concerns? ===
>
> * N/A
>
> Thanks,
> Nicholas
>
>