Jump to: navigation, search

ECF 2.0.0/Ganymede Ramp-Down Policy

Revision as of 09:55, 29 April 2008 by Slewis.composent.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Ramp Down for ECF 2.0.0/Ganymede

This policy refers to listed components of Eclipse Communication Framework Project version 2.0.0.

When referring to API freeze, we mean public API for the ECF plugins only (those in CVS at /cvsroot/technology/org.eclipse.ecf/plugins, and providers), NOT internal API for these plugins, incubating ECF plugins (in incubation/plugins), or plugins hosted at the Oregon State University Open Source Lab].

ECF does daily builds and weekly integration builds. We are working to get our test plugins run as part of the automated build before RC1. When the automated testing is in place, all tests in all test plugins (in /cvsroot/technology/org.eclipse.ecf/test) will pass before plugins will be considered stable and released.

ECF committers are expected to run the test plugins associated with the plugins that are being modified (e.g. org.eclipse.ecf.tests.datashare for org.eclipse.ecf.datashare) before every change (enhancement or bug fix).

Documentation fixes will be allowed up until time of release.

Note: ECF has six plugins/fragments that are required for p2 and therefore also the Eclipse platform:

  • org.eclipse.ecf, org.eclipse.ecf.identity, org.eclipse.ecf.filetransfer, org.eclipse.ecf.provider.filetransfer, org.eclipse.ecf.ssl, org.eclipse.ecf.provider.filetransfer.ssl

For these plugins, the ECF build and ramp-down will follow the Platform Build Schedule. Other than bug fixes, no changes are to be applied to these plugins after M7+0, and after RC3+0 no changes are to be applied at all. Further, any changes to these plugins after M7 will need to be approved by the project lead and 2 other ECF committers.

Policy by Milestone

M6

ECF has it's API freeze for the six platform plugins (as described above) at M6+0. Beyond M6, until ECF 2.0.0 is released, no API changes are planned or expected for these six plugins.

If some unexpected API change is required (e.g. in order to support the use of ECF for p2 and/or the Eclipse platform), then this will only be done after a positive vote of the ECF committers (i.e. majority of +1, no -1).

M7

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

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

RC1

ECF 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