Jump to: navigation, search

Difference between revisions of "Fuel/Soft Code Freeze"

(Created page with "'''Soft Code Freeze''' - last day when we accept bugfixes into master with priority < High. After this day, we merge only High & Critical priority bug fixes. For exceptional b...")
 
(stable branch is created at SCF)
 
Line 1: Line 1:
'''Soft Code Freeze''' - last day when we accept bugfixes into master with priority < High. After this day, we merge only High & Critical priority bug fixes. For exceptional bugs, we can increase priority and provide explanation how risky it is in terms of breaking other features. Remained Medium & Low priority bugs are moved to next release, some of them are being documented as Known Issues.
+
'''Soft Code Freeze''' (SCF) is a time-based milestone in the Fuel release cycle that marks the point after which only High and Critical bug fixes are allowed in the release branch.
 +
 
 +
Once SCF is announced:
 +
 
 +
* stable branch is created for the release
 +
* only fixes for High and Critical bugs are allowed in the stable branch
 +
* commits to the stable branch must follow the [[Fuel/How_to_contribute#Backport_bugfixes_to_stable_release_series|backporting process]]: only propose a stable backport after the fix was merged in the master branch
 +
* master branch is open for feature development for the next release and for Medium and lower priority bug fixes
 +
 
 +
Rationale: restricting stable branch to High and Critical bugfixes encourages the team to focus on a smaller number of bugs, and reduces the number of regressions introduced by commits merged into the stable branch.

Latest revision as of 22:23, 17 December 2015

Soft Code Freeze (SCF) is a time-based milestone in the Fuel release cycle that marks the point after which only High and Critical bug fixes are allowed in the release branch.

Once SCF is announced:

  • stable branch is created for the release
  • only fixes for High and Critical bugs are allowed in the stable branch
  • commits to the stable branch must follow the backporting process: only propose a stable backport after the fix was merged in the master branch
  • master branch is open for feature development for the next release and for Medium and lower priority bug fixes

Rationale: restricting stable branch to High and Critical bugfixes encourages the team to focus on a smaller number of bugs, and reduces the number of regressions introduced by commits merged into the stable branch.