Jump to: navigation, search

Difference between revisions of "Fuel/Hard Code Freeze"

m (updated criteria for bugs which don't participate in HCF)
Line 5: Line 5:
 
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.
 
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:
+
Bugs, which currently do not participate in HCF criteria calculation:  
* DevOps related (Fuel Infra)
+
* DevOps related (Fuel Infra, marked by 'devops' tag)
* QA-related (system tests, etc.)
+
* QA-related (system tests, etc.. marked by 'system-tests' tag or assigned to QA team)
* Documentation bugs
+
* Documentation bugs (marked by 'docs' tag or assigned to documentation team)
 
* Bugs against experimental features (marked by 'experimental' tag)
 
* Bugs against experimental features (marked by 'experimental' tag)
 +
* Bugs which are not related to product artefacts (marked by 'non-release' tag)

Revision as of 11:37, 14 September 2015

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:

  • 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 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:

  • DevOps related (Fuel Infra, marked by 'devops' tag)
  • QA-related (system tests, etc.. marked by 'system-tests' tag or assigned to QA team)
  • Documentation bugs (marked by 'docs' tag or assigned to documentation team)
  • Bugs against experimental features (marked by 'experimental' tag)
  • Bugs which are not related to product artefacts (marked by 'non-release' tag)