Skip to main content
Jump to: navigation, search

ECF Kepler Ramp-Down Policy

Ramp Down for ECF 3.6.1/Kepler Release

This policy refers to all components of ECF version 3.6.1.

When referring to API freeze, we mean public API for the ECF plugins only (those in git repos), NOT internal API for these plugins, incubating ECF plugins (in incubation/bundles), or plugins hosted at github.

ECF does daily continuous integration builds and will have integration release builds on May 3, May 10, and May 21.

May 21 will be our final planned release build for Kepler release.

All documentation-only fixes will be allowed up until time of release.

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

  • 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, org.eclipse.ecf.provider.filetransfer.httpclient4, org.eclipse.ecf.provider.filetransfer.httpclient4.ssl

For these plugins, the ECF build and ramp-down will follow the Platform freeze plan. 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


ECF has it's API freeze for all plugins at M7+0. Beyond M7, until final release, no API changes are planned or expected for any ECF plugins.

If some unexpected/emergency 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).


ECF will have it's feature freeze at RC1+0 (May 17). This will mean no new/additional user-visible features will 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 RC4+0.

Back to the top