Difference between revisions of "Fuel/Hard Code Freeze"

Latest revision as of 23:42, 17 December 2015

Hard Code Freeze (HCF) is a quality-based milestone in the Fuel release cycle that marks availability of the first release candidate (RC1), after which only Critical bug fixes are allowed in the release branch.

Entry criteria:

swarm (fuel-qa/system_tests) pass rate is above 90%
less than 5 open High bugs, no open Critical bugs
less than 30 High and less than 10 Critical bugs were closed during the previous week

If HCF entry criteria are not met on schedule, HCF should be postponed.

If Critical bugs are found in an RC, more RCs are produced iteratively until QA team confirms that the latest RC is suitable for a stable release.

Just as with Soft Code Freeze, commits to the stable branch during and after HCF must follow the backporting process.

@@ Line 1: / Line 1: @@
-'''Hard Code Freeze''' - last day when we accept fixes on High priority bugs. When we reach hard code freeze, we should have 0 critical bugs and no more than 5 high priority bugs open. If we have more high priority bugs, or even one critical, we move hard code freeze unless the condition is met. When we meet this condition, and hard code freeze is announced, then it is being announced with information about stable branch created and Release Candidate is created. It is the time when master opens for next release changes, including features. Critical bugs, if found after this day, cause the following procedure:
+'''Hard Code Freeze''' (HCF) is a quality-based milestone in the Fuel release cycle that marks availability of the first release candidate (RC1), after which only Critical bug fixes are allowed in the release branch.
-* Fix is proposed to both master & stable/<rel-version> branch. It must be merged into master first, and core developers only approve patches into stable branch if corresponding patchset with same ChangeID was accepted into master
-* New RC is created
-QA team starts final acceptance testing on RC. If new RC is created, we respin acceptance cycle. Process is repeated unless we get a stable release version. It is done in a [[Release_Cycle#Other_release_candidates|similar way for OpenStack]].
-There can be exception though, when we don't need to respin a cycle. It happens, if change is considered to be local to very limited affection area. PTL & core development leads decide whether it is the case.
-Bugs, which currently do not participate in HCF criteria calculation:
+Entry criteria:
-* DevOps related (Fuel Infra)
-* QA-related (system tests, etc.)
+* swarm ([http://git.openstack.org/cgit/openstack/fuel-qa/tree/system_test fuel-qa/system_tests]) pass rate is above 90%
-* Documentation bugs
+* less than 5 open High bugs, no open Critical bugs
-* Bugs against experimental features (marked by 'experimental' tag)
+* less than 30 High and less than 10 Critical bugs were closed during the previous week
+If HCF entry criteria are not met on schedule, HCF should be postponed.
+If Critical bugs are found in an RC, [[Release_Cycle#Other_release_candidates|more RCs are produced iteratively]] until QA team confirms that the latest RC is suitable for a stable release.
+Just as with [[Fuel/Soft_Code_Freeze|Soft Code Freeze]], commits to the stable branch during and after HCF must follow the [[Fuel/How_to_contribute#Backport_bugfixes_to_stable_release_series|backporting process]].