Skip to main content

Table 1 The three feature freezes of OpenStack

From: Managing to release early, often and on time in the OpenStack software ecosystem

Freeze Description
FeatureFreeze Project teams are requested to stop merging code adding new features, new dependencies, new configuration options, database schema changes, changes in strings... all things that make the work of packagers, documenters or testers more difficult.
SoftStringFreeze After the FeatureFreeze, translators start to translate the strings. To aid their work, any changes to existing strings is avoided, as this will invalidate some of their translation work. New strings are allowed for things like new log messages, as in many cases leaving those strings untranslated is better than not having any message at all.
HardStringFreezee 10 days after the SoftStringFreeze, any string change after RC1 should be discussed with the translation team.