FeatureFreeze
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 detailled upstream changelog and (cursory) reading the diff between the version in the Ubuntu 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. For the purpose of the FeatureFreeze, the upload date matters, i. e. all packages which are in the NEW queue by that time will be processed without the need for an exception.
FeatureFreeze for Jaunty was originally scheduled for mid-February. But seeing that DebianImportFreeze was delayed, it may be a few days out.