Jump to: navigation, search

EPP/Galileo Ramp-Down Policy

< EPP
Revision as of 05:15, 6 May 2009 by Mknauer.eclipsesource.com (Talk | contribs)

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

Ramp Down for EPP 1.1.0/Galileo

This policy refers to the following components of EPP version 1.1.0:

  • org.eclipse.epp.usagedata.*

When referring to API freeze, we mean public API for the EPP plugins only (those in CVS at /cvsroot/technology/org.eclipse.epp/plugins/ that we include in Galileo), and NOT internal API for these plugins.

EPP committers are expected to run the test fragments associated with the plugins that are being modified (e.g. org.eclipse.epp.packaging.core.test for org.eclipse.epp.packaging.core) before every change (enhancement or bug fix).

Documentation fixes will be allowed up until time of release.

Policy by Milestone

Galileo M6 API Freeze

EPP has it's API freeze at M6 EPP. Beyond M6, until EPP 1.1.0 is released, no API changes are planned or expected for any EPP plugins.

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

Galileo M7

EPP will have it's feature freeze at Galileo M7. 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 one other committer have agreed to and then separately tested the fix.

Galileo RC1 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.

See Also