Difference between revisions of "Feature freeze"
(→UI/Feature Freeze) |
(removed integration deadline) |
||
| Line 10: | Line 10: | ||
Usually we use a combined UI and Feature freeze at the same date. At this date all UI changes and all new Features need to beintegrated into the code base. Last translation will be handed over to translation teams. All Features must have been completed to ensure that there is enough time to review the new feature before the next release and incorporate feedback. For OpenOffice.org this is usually 9 weeks before release. | Usually we use a combined UI and Feature freeze at the same date. At this date all UI changes and all new Features need to beintegrated into the code base. Last translation will be handed over to translation teams. All Features must have been completed to ensure that there is enough time to review the new feature before the next release and incorporate feedback. For OpenOffice.org this is usually 9 weeks before release. | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 15:37, 1 September 2009
UI Freeze
At this point all UI changes need to beintegrated into the code base. Last strings for translation will be handed over to localization teams. For OpenOffice.org this is usually 9 weeks before release.
Feature Freeze
At this point all new Features need to be integrated into the code base. All Features must have been completed to ensure that there is enough time to review the new feature before the next release and incorporate feedback. For OpenOffice.org this is usually 9 weeks before release.
UI/Feature Freeze
Usually we use a combined UI and Feature freeze at the same date. At this date all UI changes and all new Features need to beintegrated into the code base. Last translation will be handed over to translation teams. All Features must have been completed to ensure that there is enough time to review the new feature before the next release and incorporate feedback. For OpenOffice.org this is usually 9 weeks before release.
