Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "DLTK/Ganymede Ramp-Down Policy"

Line 13: Line 13:
  
 
===RC1===
 
===RC1===
DLTK will have it's feature freeze at RC1+1 (May 20).  This will mean no new/additional user-visible features will be planned or expected to be introduced beyond this point.   
+
DLTK will have it's feature freeze at RC1+1 (May 19).  This will mean no new/additional user-visible features will be planned or expected to be introduced beyond this point.   
  
 
If a user-visible feature change must occur to address a major or critical bug, the fix will only be applied after the project lead and 3 other committers have agreed to and then separately tested the fix.
 
If a user-visible feature change must occur to address a major or critical bug, the fix will only be applied after the project lead and 3 other committers have agreed to and then separately tested the fix.

Revision as of 07:04, 6 May 2008

Ramp Down for DLTK 1.0/Ganymede

This policy refers to listed components of DLTK Project version 1.0.0.

When referring to API freeze, we mean public API for the DLTK components only that we contribute Ganymede, and NOT internal API for these plugins, nor for incubating DLTK plugins (not included in Ganymede).

Policy by Milestone

M7

DLTK has it's API freeze at M7+1. Beyond M7, until DLTK 1.0.0 is released, no API changes are planned or expected for any DLTK plugins.

If some unexpected API change is required, then this will only be done after a positive vote of the Buckminster committers (i.e. majority of +1, no -1).

RC1

DLTK will have it's feature freeze at RC1+1 (May 19). This will mean no new/additional user-visible features will be planned or expected to be introduced beyond this point.

If a user-visible feature change must occur to address a major or critical bug, the fix will only be applied after the project lead and 3 other committers have agreed to and then separately tested the fix.

RC2 to Release

Primary activity will be in testing, reporting, and addressing major or higher bugs. Documentation additions and changes can and will continue until 3 days before Ganymede Release (June 22).

See Also

Back to the top