QualityImprovements

Goals

  • Maintain higher quality throughout the development releases in order to:
    • Promote more testing and usage of the stable release
    • Maintain a higher Quality/Feature ratio
    • Increase predictability of good quality release
  • Increase focus on users of stable release in order to:
    • Respond faster to known and unknown issues after release
    • Improve the responsiveness to customers of the stable release
    • Minimize risk of regressions during the stable release

Development Release

Phase

Plan

Owners

Notes

Pre-Commit

Acceptance Criteria

robbiew, jasoncwarner, skaet

Pre-Commit

Test Suites (Canonical Code)

??

Pre-Commit

Test Suites (Other Upstreams)

pgraner

Pre-Commit

Test Suites (Integration)

pgraner

Post-Commit

Testing Gauntlet

pgraner

Post-Commit

Daily Automated Testing

pgraner

Post Commit

Daily Usage Testing

jono, DAs??

Alphas and Betas

More Robust Resleases

skaet

Alphas and Betas

More Automated, Less Effortful Releases

skaet

Alphas and Betas

More Community Testers

jono

Alphas and Betas

Prioritizing Bug Reports

DAs

Alphas and Betas

Fixing Bugs before New Features

EMs, skaet??

Ongoing

Launchad Data Mining

DAs

Ongoing

Prioritized Bug Lists

DAs

Ongoing

Bug fixing prioritized over feature development

DAs, skaet

Stable Release

Phase

Plan

Owners

Notes

Post Releases

Identification of worst bugs

DAs

Ongoing

Fixing of worst bugs

Engineering Managers

Ongoing

SRUs

Stable Release Team, skaet

Ongoing

L3 Support Process

Jose

UbuntuEngineering/12.04/QualityImprovements (last edited 2011-08-16 14:52:48 by rick-rickspencer3)