The PMC
discussed the following 1.0 endgame plan on the call this morning. Our goal is
to ship a quality release usable by adopters, with a controlled rampdown from
M9 to final product. API definitions and documentation are also critical to
this release; please see separate email regarding the API plan. The current number
of defects is a significant risk, so any additional effort you can spend on
lowering the bug count would be appreciated and would help us address these concerns.
M9:
- Scheduled for Wednesday, November 23
Post M9:
- Any API changes (addition, deletion, or
modification) require PMC approval
- All checkins require a Bugzilla entry
- PMC will review defect convergence on a weekly
basis (daily as needed during final RC candidate production)
Between M9 and RC1:
- All P1 bugs addressed, all P2 bugs reviewed for
fix need prior to RC1 production
- No API or infrastructure changes; updates to UI
ok
November 30:
- RC1 produced
- Bug fixes and UI changes only (versus M9)
- All checkins must have Bugzilla entry
- Component lead must code review and approve all
fixes (enter into Bugzilla record and checkin notes)
December 7:
- RC2 produced
- Same rules as above, plus P1/2 only can be
addressed
- Changes communicated to wtp-dev mailing list
- Component lead and PMC must approve all
changes (versus RC2)
- All changes communicated to wtp-dev mailing
list
December 9:
- Cutoff for RCs before entering the 1-week “cooldown”
period
December
16:
- 1.0 GA release by renaming latest RC
- If ship-killer (no workaround) defects are
discovered, we will produce RC N+1 and restart the one-week cooldown
Release criteria:
- No P1’s admitted (i.e., no ship-killer
defects known)
- All automated tests passing on final RC
- Tier-1 platforms have been tested
- All component leads sign off on individual
components
- PMC votes to release
|
