Feature Freeze

At this point we stop introducing new features, packages, and APIs, and concentrate on fixing bugs in the development release.

Exceptions have to be approved by the release management team. They should be granted if the new package or feature

  • contributes to high-priority ReleasenameFeatureGoals,

  • is a reasonable fix for an important bug,
  • other exceptional circumstances, as judged by the release managers.

See FreezeExceptionProcess for details.

Notes about particular aspects of features:

  • Upstream microreleases of applications are usually fine after this point if they only fix bugs. This should be verified by reading the detailed upstream changelog and (cursorily) reading the diff between the version in the Linaro development release and the new upstream version. If in doubt, ask the release team for advice.
  • ABI/API compatibility is a special case of a feature: If a library breaks backward compatibility (i. e. changes existing API/ABI and introduces a new SONAME), then this always needs approval from the release team, since all reverse dependencies need to be adjusted and rebuilt.

  • New packages need to be checked by archive administrators before they find their way into the archive. This process can take several days up to a few weeks.

Sample mailing list announcements

One week before feature freeze, sent to the linaro-announce and linaro-dev lists from the 10.11 cycle:


According to the schedule [1] the Linaro Feature Freeze will be in 
effect from 2010-08-12, i.e. Thursday. This signals our transition 
from adding new features to bug fixing and improving what is already 
there. Exceptions to this process will have to be approved by the 
release management team [2] using the Feature Freeze exception 
process [3]. After this date your new features are not guaranteed to 
be in the next release so please try to get your enhancements in as 
soon as possible. For an explanation of the Feature Freeze process 
please see the wiki [4].

Linaro Release Manager

[1] https://wiki.linaro.org/Releases/1011#Linaro10.11Schedule
[2] https://edge.launchpad.net/~linaro-release
[3] https://wiki.linaro.org/Releases/FreezeExceptionProcess
[4] https://wiki.linaro.org/Releases/FeatureFreeze 

On the actual date of Feature Freeze, sent to the linaro-announce and linaro-dev, from the 10.11 cycle:


Linaro is now in Feature Freeze[1] and effort should switch to bug
fixing and polish. If you believe that your new feature or package
needs to be in the 10.11 Linaro release please follow the Feature
Freeze Exception process [2] as soon as possible.  

Beta 1 is in 3 weeks [3] so please use this time to stabilize and
improve what we already have in Linaro to ensure that the 10.11 
release is as solid as possible.

Linaro Release Manager

[1] https://wiki.linaro.org/Releases/FeatureFreeze
[2] https://wiki.linaro.org/Releases/FreezeExceptionProcess
[3] https://wiki.linaro.org/Releases/1011#Linaro10.11Schedule

Taken and adapted from the Ubuntu wiki page of the same name

CategoryProcess, CategoryRelease

internal/archive/Process/Cycle/FeatureFreeze (last modified 2013-08-28 13:10:10)