Commit log annotation-driven auto-backports

Registered by Tom Fifield on 2013-10-16

There have been several bugs in the stable branches that were fixed in the master but hadn't been backported to the stable branch. This blueprint proposes the following automated approach to ensure backports happen more regularly:

Any patch to the master branch must specify in the commit message whether the patch should be backported. For example:

backport: havana

or

backport: none

or

backport: havana grizzly

If this line is missing from the commit log, then a gating job will fail, and jenkins will link to the error message (e.g., "Missing 'backport: ' line. Please specify "backport: havana" if this should be backported to havana or "backport: none" if this shouldn't be backported).

When the patch is merged into trunk, then jenkins automatically does a cherry-pick and merge proposal against the branches specified in the backport line.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Low
Drafter:
Lorin Hochstein
Direction:
Approved
Assignee:
None
Definition:
Obsolete
Series goal:
Accepted for liberty
Implementation:
Not started
Milestone target:
None
Completed by
Lana

Related branches

Sprints

Whiteboard

Mark McLaughlin may have some scripts to help
it's a "nice to have"
Is this a discussion which really needs to be had in the scope of infra? does it affect any other project? No, but it sounds like infra *work*.

(shardy) Can anyone please link to the implementation of this? There are no work items or links to patches, yet it's marked implemented. We need something exactly like this for TripleO. Thanks!

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.