User Tools

Site Tools


fuel_opnfv_guidelines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
fuel_opnfv_guidelines [2015/10/02 17:33]
Jonas Bjurel [Verifying a patch]
fuel_opnfv_guidelines [2015/10/05 19:01] (current)
Jonas Bjurel
Line 11: Line 11:
   * Step down considerately:​ Members of every project come and go. When somebody leaves or disengages from the project, they should make it known and take the proper steps to ensure that others can pick up where they left off.   * Step down considerately:​ Members of every project come and go. When somebody leaves or disengages from the project, they should make it known and take the proper steps to ensure that others can pick up where they left off.
  
 +===== JIRA procedures =====
 +TBW
  
 ===== Commit procedures ===== ===== Commit procedures =====
Line 25: Line 27:
 **VERIFIED/​NOT VERIFIED** - indicates weather the commit has passed the developers pipeline verification. **VERIFIED/​NOT VERIFIED** - indicates weather the commit has passed the developers pipeline verification.
  
-**JIRA: JIRA-ID** - indicates the JIRA-ID to which the commit refers to, use BUG as a JIRA reference if it refers to a non reported bug.+**JIRA: JIRA-ID** - indicates the JIRA-ID to which the commit refers to, use **BUG** or **IMPROVEMENT** ​as a JIRA reference if it refers to a non reported bug/​improvement.
  
 **DESCRIPTION:​ A short commit description** **DESCRIPTION:​ A short commit description**
Line 36: Line 38:
   * Usee 0 if you just want to communicate through the comment field, 0 without any comments doesn'​t make sense and shall be avoided.   * Usee 0 if you just want to communicate through the comment field, 0 without any comments doesn'​t make sense and shall be avoided.
   * Use +1 if you agree with the patch, don't vote +1 on your own patches.   * Use +1 if you agree with the patch, don't vote +1 on your own patches.
-  * Use +2 if you agree with the patch and want it merged, don't vote +2 on your own patches unless the project lead agrees and don't vote +2 until a chorum has voted +1 or a 24 hour period has passed.+  * Use +2 if you agree with the patch and want it merged, don't vote +2 on your own patches unless the project lead agreesand don't vote +2 until a chorum has voted +1 or a 24 hour period has passed.
  
 ===== Merge procedures ===== ===== Merge procedures =====
Line 50: Line 52:
 ===== Branches ​ ===== ===== Branches ​ =====
 We are generally cautious and restrictive in creating branches. We are generally cautious and restrictive in creating branches.
-Normally we only work out of the master branch until code-freeze - about weeks before a major release.+Normally we only work out of the master branch until code-freeze - about four weeks before a major release.
  
 At code-freeze of a major release, a stable branch is created. During the time from code freeze of a stable release until the release - any fixes shall first be merged and tested on master, and after having passed a nightly build/​deploy be cherry picked to the stable branch. At code-freeze of a major release, a stable branch is created. During the time from code freeze of a stable release until the release - any fixes shall first be merged and tested on master, and after having passed a nightly build/​deploy be cherry picked to the stable branch.
fuel_opnfv_guidelines.1443807225.txt.gz ยท Last modified: 2015/10/02 17:33 by Jonas Bjurel