Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-dev] Endgame: updated rampdown plan



Here is the plan the PMC approved [1]. It was posted on the pmc list, so I thought it would be useful to repost it here.

[1] http://dev.eclipse.org/mhonarc/lists/wtp-pmc/msg00118.html
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)
 

Prior to initial RC:

  • All P1 bugs addressed, all P2 bugs reviewed for fix need prior to RC cut
 

July 13:

  • RC1 produced
  • Only non-destabilizing bug fixes, P3 and above. User impact and cosmetic fixes only will be approved; no API changes
  • All checkins must have Bugzilla entry
  • Component lead must code review and approve all fixes (enter into Bugzilla record and checkin notes)
 

July 22:

  • RC2 produced
  • P1/2 only can be addressed
  • All checkins must have Bugzilla entry
  • Component lead and PMC member must code review and approve
  • Changes communicated to wtp-dev mailing list
 

Additional RCs as directed by PMC:

  • P1 only can be addressed
  • Component lead and PMC must approve all changes
  • All changes communicated to wtp-dev mailing list
 

 

Release guidelines:

  • 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

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
intranet: http://labweb.torolab.ibm.com/DRY6/

Back to the top