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

Bug 253434

Summary:	Ramp Down Policy
Product:	[Modeling] EMF	Reporter:	Anne Jacko <anne.jacko>
Component:	Releng	Assignee:	Nick Boldt <nboldt>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P1	CC:	davidms, mtaal, stepper
Version:	unspecified
Target Milestone:	M5
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	252792

Description Anne Jacko

2008-11-03 18:26:21 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 Eike Stepper

2008-12-11 15:48:28 EST

I think this is handled on sub-project level? I.e. EMF

Comment 2 Martin Taal

2008-12-11 16:08:56 EST

Same thought from me (for Teneo)

Comment 3 Christian Damus

2009-03-18 20:07:38 EDT

The following components adhere to the Eclipse Modeling Project's common ramp-down policy:

Query
Transaction
Validation

Comment 4 Dave Steinberg

2009-03-25 22:44:43 EDT

EMF will adhere to the Modeling Project ramp down policy:
http://wiki.eclipse.org/Modeling_Project_Ramp_Down_Policy/Galileo

Comment 5 Ed Merks

2018-01-22 11:36:15 EST

Closing all fixed releng bugs.