Difference between revisions of "Feature freeze"

From Apache OpenOffice Wiki
Jump to: navigation, search
(UI Freeze)
m
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
== UI Freeze ==
 
== UI Freeze ==
 
+
At this point all UI changes need to be integrated into the code base. Last strings for translation will be handed over to localization teams. For OpenOffice.org this is usually 9 weeks before a release.
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 ==
 
== 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 them before the next release and incorporate feedback. For OpenOffice.org this is usually 9 weeks before a release.
At this point all new Features need to be approved by QA or nominated for integration 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 ==
 
== UI/Feature Freeze ==
 +
Nowadays we use a combined UI and Feature Freeze at the same date. At this date all UI changes and all new features have to be integrated 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 them before the next release and incorporate feedback. For OpenOffice.org this is usually 9 weeks before a 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 be approved by QA or nominated for integration 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.
+
[[Category:Releases]]
 
+
== nomination deadline ==
+
 
+
qa approval or nominations should be done until 11.59 pm UTC of that days, so that integration of these child workspaces can be performed the next day
+

Latest revision as of 11:54, 13 December 2010

UI Freeze

At this point all UI changes need to be integrated into the code base. Last strings for translation will be handed over to localization teams. For OpenOffice.org this is usually 9 weeks before a 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 them before the next release and incorporate feedback. For OpenOffice.org this is usually 9 weeks before a release.

UI/Feature Freeze

Nowadays we use a combined UI and Feature Freeze at the same date. At this date all UI changes and all new features have to be integrated 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 them before the next release and incorporate feedback. For OpenOffice.org this is usually 9 weeks before a release.

Personal tools