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

Bug 258448

Summary: Ramp Down Policy
Product: z_Archived Reporter: Roy Ganor <ganoro>
Component: PDTAssignee: Roy Ganor <ganoro>
Status: CLOSED INVALID QA Contact:
Severity: normal    
Priority: P1 CC: bruck.james, gadi, kalin.a, silviya
Version: unspecifiedKeywords: plan
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 252792    
Bug Blocks:    

Description Roy Ganor CLA 2008-12-11 09:54:13 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 Roy Ganor CLA 2009-01-07 02:16:28 EST
these are clones of 
260135,	260136,	 260138, 260139, 260140, 260141, 260142, 260143, 260144, 260145, 260146, 260147, 260148, 260149, 260150, 260151, 260152, 260153, 260154, 260155, 260156, 260157, 260158, 260159, 260160, 260161, 260162


Comment 2 Gadi Goldbarg CLA 2009-01-30 06:57:10 EST
I'm closing it as a clone of Bug #252792
Kalin Yanev
kalin.a@zend.com