Buckminster/Ganymede Ramp-Down Policy
Ramp Down for Buckminster 1.1/Ganymede
This policy refers to listed components of Buckminster Project version 1.1.0.
When referring to API freeze, we mean public API for the Buckminster plugins only (those in SVN at /svnroot/tools/org.eclipse.buckminster/trunk that we include in Ganymede), and NOT internal API for these plugins, nor for incubating Buckminster plugins (not included in Ganymede).
Buckminster is built and published on demand. We are working to get our test fragments run as part of the automated build before RC1. When the automated testing is in place, all tests in all test fragments will pass before plugins will be considered stable and released.
Buckminster committers are expected to run the test fragments associated with the plugins that are being modified (e.g. org.eclipse.buckminster.core.test for org.eclipse.buckminster.core) before every change (enhancement or bug fix).
Documentation fixes will be allowed up until time of release.
Policy by Milestone
Buckminster has it's API freeze at M7+2. Beyond M7, until Buckminster 1.1.0 is released, no API changes are planned or expected for any Buckminster 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).
Buckminster will have it's feature freeze at RC1+2 (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 Ganymede Release (June 22).