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

Bug 253442

Summary:	Ramp Down Policy
Product:	[Eclipse Project] Equinox	Reporter:	Anne Jacko <anne.jacko>
Component:	Framework	Assignee:	equinox.framework-inbox <equinox.framework-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P1	CC:	tjwatson
Version:	unspecified
Target Milestone:	3.5 M7
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	252792

Description Anne Jacko

2008-11-03 18:31:36 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 Thomas Watson

2008-11-05 14:19:48 EST

We will have a ramp-down policy in place by M6.  It will be similar to the ramp down policy used for the Eclipse Project last release (http://www.eclipse.org/eclipse/development/freeze_plan_3.4.php).

Comment 2 Thomas Watson

2009-04-03 14:58:50 EDT

Done.

http://www.eclipse.org/equinox/planning/freeze_plan_3.5.php