Open Stack

I created a blueprint for this proposal:

https://blueprints.launchpad.net/openstack-manuals/+spec/attempt-backport-by-commit-message

On 02/06/13 11:40, Lorin Hochstein wrote:
> All:
> 
> I've noticed that there have been several bugs in the grizzly branch
> that were fixed in the master but hadn't been backported to
> stable/grizzly. I'd like to propose 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: stable/grizzly
> 
> or
> 
> backport: none
> 
> or
> 
> backport: stable/grizzly stable/folsom
> 
> 
> 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: stable/grizzly" if this
> should be backported to grizzly 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.
> 
> 
> What do you folks think?
> 
> 
> Lorin
> 
> -- 
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com <http://www.nimbisservices.com>
> 
> 
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>