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
Last revision Both sides next revision
fuel_opnfv_guidelines [2015/10/03 17:06]
Jonas Bjurel
fuel_opnfv_guidelines [2015/10/05 19:00]
Jonas Bjurel [Commit procedures]
Line 27: 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 IMROVEMENT ​as a JIRA reference if it refers to a non reported bug/​improvement.
  
 **DESCRIPTION:​ A short commit description** **DESCRIPTION:​ A short commit description**
Line 38: 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 =====
fuel_opnfv_guidelines.txt ยท Last modified: 2015/10/05 19:01 by Jonas Bjurel