Jump to: navigation, search


Revision as of 16:43, 18 February 2013 by ThierryCarrez (talk | contribs)

FeatureFreeze (FF) happens when we create the milestone-proposed branch for the last development milestone in a cycle. It generally happens late on the Tuesday (or early on the Wednesday) on the corresponding milestone delivery week.


Once FF kicks in, you are no longer allowed to accept proposed changes containing new features into the current development release. Such proposed changes should be rejected by the review team and postponed until the next series development opens (which should happen when RC1 is published).


FF ensures that sufficient share of the ReleaseCycle is dedicated to QA, until we produce the first release candidates. Limiting the changes that affect the behavior of the software allow for consistent testing and efficient bugfixing.

Exception procedure

If you want to propose changes containing a feature (that you believe has an acceptable importance/risk_of_regression ratio) for merging into the development release after FF, follow those steps:

  • Make sure all your change has thorough unit tests, especially if your patch touches an area of the code that currently is not well-tested
  • Make sure the proposed change is linked to the associated blueprint (if any)
  • Propose your change for merging
  • In a specific comment on the review, provide the following information:
    • Benefit of the change
    • Risk of regression
  • In the review, request the advice of the Release Manager by adding his name using "Add reviewer"

You can check who is the current Release Manager by looking at the current Release schedule.

The Release manager, with the assistance of the core developers of the associated product, will evaluate the request and grant or deny the exception. The farther we are in the release cycle, the less likely it is for the exception to be granted. Remember that the next cycle is just a month away :)