Bug 253439 - Ramp Down Policy
Summary: Ramp Down Policy
Status: CLOSED FIXED
Alias: None
Product: MDT
Classification: Modeling
Component: Releng (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P1 normal (vote)
Target Milestone: M5   Edit
Assignee: Dummy mdt releng inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 252792
  Show dependency tree
 
Reported: 2008-11-03 18:29 EST by Anne Jacko CLA
Modified: 2016-10-06 13:05 EDT (History)
5 users (show)

See Also:
Kenn.Hussey: galileo+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Anne Jacko CLA 2008-11-03 18:29:53 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 Kenn Hussey CLA 2008-12-19 10:19:50 EST 
SBVR will not be on the train.
Comment 2 Kenn Hussey CLA 2009-03-18 11:17:04 EDT 
MDT components will adhere to the Modeling Project ramp-down policy, which can be found at http://wiki.eclipse.org/Modeling_Project_Ramp_Down_Policy.
Comment 3 Kenn Hussey CLA 2016-10-06 13:05:40 EDT 
Closing, as this bug has been fixed for some time.