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

Bug 253432

Summary:	Ramp Down Policy
Product:	[Tools] Target Management	Reporter:	Anne Jacko <anne.jacko>
Component:	Core	Assignee:	Martin Oberhuber <mober.at+eclipse>
Status:	RESOLVED FIXED	QA Contact:	Martin Oberhuber <mober.at+eclipse>
Severity:	normal
Priority:	P1
Version:	unspecified
Target Milestone:	3.1 M2
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	252792

Description Anne Jacko

2008-11-03 18:24:57 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 Martin Oberhuber

2009-01-07 12:42:02 EST

TM Policy: http://wiki.eclipse.org/DSDP/TM/3.1_Ramp_down_Plan