[ovirt] #104: accept only backports into stable branches

ovirt trac at fedorahosted.org
Tue Jan 7 12:52:55 UTC 2014

#104: accept only backports into stable branches
  Reporter:  danken   |      Owner:  infra@…
      Type:  task     |     Status:  new
  Priority:  major    |  Milestone:  oVirt 3.4
 Component:  Jenkins  |    Version:
  Severity:  High     |   Keywords:
Blocked By:           |   Blocking:
 A stable branch, such as ovirt-3.3, should only carry code from the master
 branch, unless we have a very good reason.

 Please add a bot verifying that.

 Each branch should have its "controller" branch defined. The "controller"
 branch of ovirt-3.3 is "master". If we create an ovirt-3.3.4 branch, its
 controller is ovirt.3.3.

 When a patch is submitted to a branch, its Change-Id is to be checked. The
 same Change-Id should exist in the controller branch.

 There should be an exception to this general rule: if a patch is submitted
 to the ovirt-3.3.4 branch and its commit message has a line saying

   Label: ovirt-3.3.4-only

 we should not require that it exists on the controller branch. This is
 useful for cases where the specific branch is broken.

Ticket URL: <https://fedorahosted.org/ovirt/ticket/104>
ovirt <http://www.ovirt.org/>
oVirt - virtualization made easy.

More information about the Infra mailing list