Difference between revisions of "DLTK/Ramp Down Policy-1.0"
(New page: When referring to API freeze, we mean public API for the DLTK components only that we contribute Galileo, and NOT internal API for these plugins, nor for incubating DLTK plugins (not inclu...)
Latest revision as of 01:40, 5 May 2009
When referring to API freeze, we mean public API for the DLTK components only that we contribute Galileo, and NOT internal API for these plugins, nor for incubating DLTK plugins (not included in Galileo).
Components to be contributed to Galileo
DLTK willing to contribute following project components to Ganymede:
- Core Frameworks
- TCL IDE
- XOTcl Support for TCL IDE
- itcl Support for TCL IDE
- Ruby IDE
Following components will continue incubation with DLTK project and will not be contributed to Galileo:
Policy by Milestone
DLTK has it's API freeze at M7+3. 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 DLTK committers (i.e. majority of +1, no -1).
DLTK will have it's feature freeze at RC1+3 (May 20). 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 Galileo Release (June 19).