Open Stack

Andreas:

I like the idea of having the reviewers require this until it has been
automated. But, assuming the author does put the "backport: stable/havana"
in the commit message, who should be responsible for actually doing the
backport? Should it be the original author, or a (core) reviewer?


Lorin


On Fri, Oct 18, 2013 at 2:36 AM, Andreas Jaeger <aj at suse.com> wrote:

> The Install Guide and the Configuration Reference will need some
> backports from stable. Tom and myself discussed just on IRC how to now
> loose patches and he suggested to follow the recent blueprint (
>
> https://blueprints.launchpad.net/openstack-manuals/+spec/attempt-backport-by-commit-message
> ) and add for example
>
> backport: stable/havana
> or
> backport: none
>
> to each patch. I propose that we start adding these for changes to
> Install Guide and Configuration Reference - and during review demand them.
>
> For those that did commits to master since the branch of havana, please
> propose backports ;)
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>



-- 
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20131018/ab1f5718/attachment.html>