FeatureFreeze
|
Size: 379
Comment: imported from the old wiki
|
Size: 1656
Comment: revert comment about jaunty feature freeze which is not at all the position of the release team
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = FeatureFreeze = | At this point we stop introducing new features, packages, and APIs, and concentrate on fixing bugs in the development release. |
| Line 3: | Line 3: |
| = Feature Freeze = | Exceptions have to be approved by the release management team. They should be granted if the new package or feature |
| Line 5: | Line 5: |
| The point at which we cease creating and modifying internal features and packages. This means we're pretty much locked down for '''bugfixes only'''. | * contributes to high-priority ''Releasename''Feature''''''Goals, * is a reasonable fix for an important bug, * other exceptional circumstances, as judged by the release managers. |
| Line 7: | Line 9: |
| Exceptions requiring confirmation: | See FreezeExceptionProcess for details. |
| Line 9: | Line 11: |
| * Packages in or relating to high-priority ''Releasename''Feature''''''Goals * Major/minor fixes, within reason * Exceptional circumstances |
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 [[http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#sonameapiabi|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 Feature``Freeze, the upload date matters, i. e. all packages which are in the [[http://people.ubuntu.com/~ubuntu-archive/queue/hardy/new/|NEW queue]] by that time will be processed without the need for an exception. ---- CategoryProcess |
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 (last edited 2025-09-12 10:58:13 by sally-makin)