Updated from previous version with
comments from last week’s PMC call.
General Post M5 Process:
- All (provisional) API
changes require project lead approval
- All changes require associated
Bugzilla entry
- PMC will review defect
convergence on a weekly basis (daily as needed during final RC candidate
production)
Week of July 3:
- RC1 produced
- Any defect can be addressed
- Component lead must code review
and approve all fixes (enter into Bugzilla record and checkin notes)
Week of July 10:
- RC2 produced
- P1/2 only can be addressed
- All checkins must have Bugzilla
entry
- Component lead must code review
and approve
Week of July 17:
- RC3 produced, if needed
- P1 only can be addressed
- Project lead (or designate)
must approve; component lead must code review (enter both names into
Bugzilla record and checkin notes)
- All changes
communicated to wtp-dev mailing list
Week of July 24:
- Intent is to verify only;
RC’s produced as needed, and will likely move ship date out
- P1 only can be addressed in
additional RC's
- PMC approval required
for any changes (plus protocol from previous week)
- All changes
communicated to wtp-dev mailing list and newsgroup
Final review:
- No P1’s admitted (i.e.,
no ship-killer defects known)
- All automated tests passing on
final RC
- All shipping platforms have
been tested
- All component leads sign off on
individual components
- PMC votes to release
--------------------------------------------------------------------------------
Join CEO Alfred Chuang and CTO Mark Carges on June 15 for a unique online
event, giving you the first look at a new category of enterprise software
built specifically for Service-Oriented Architecture (SOA).
Register Now. It's Free!
http://www.bea.com/events/june15
|
