Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 253437

Summary: Ramp Down Policy
Product: [Modeling] MMT Reporter: Anne Jacko <anne.jacko>
Component: RelengAssignee: mmt web dummy inbox <mmt.web-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P1 CC: dvorak.radek, william.piers
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on:    
Bug Blocks: 252792    

Description Anne Jacko CLA 2008-11-03 18:28:38 EST 
+++ This bug was initially created as a clone of Bug #252792 +++

Projects must have a written ramp down policy by M6+0, linked in the table above pending inclusion of ramp down element in the XML project plan. (One of the issues identified with this guideline is that its not so much the ramp down policy of how many votes are needed for each bug fix that we need to be consistent on, but rather the meaning of each of the milestones and release candidates. See Platform 3.4 Endgame plan as a guideline. See also Galileo Final Daze.)
Comment 1 William Piers CLA 2009-04-07 08:30:26 EDT 
ATL conforms to the Modeling ramp down policy:
http://wiki.eclipse.org/Modeling_Project_Ramp_Down_Policy/Galileo
Comment 2 Radomil Dvorak CLA 2009-05-05 06:44:36 EDT 
'QVT Operational' will adhere to the Modeling Project ramp down policy:
http://wiki.eclipse.org/Modeling_Project_Ramp_Down_Policy/Galileo
Comment 3 Ed Willink CLA 2012-07-12 15:02:08 EDT 
Closing bugs resolved in Indigo