openstack-doc-core team mailing list archive

[Lorin Hochstein <lorin@xxxxxxxxxxxxxxxxxx>]

I guess we should either:

a. Ask submitters to submit to the stable/essex branch in our +2 reviews
b. Somebody from core should submit accepted master submissions to stable/essex, setting the original submitter as the author.

I put some docs up on how to do cherry picking here: http://wiki.openstack.org/Documentation/HowTo#How_to_a_cherry-pick_a_change_to_a_stable_branch

We could also ask the CI guys to set up a Jenkins job that will run, say, one week after a branch lands in master, and checks to see if there's a corresponding cherry-pick in stable/essex, it sends out an email to openstack-doc-core saying "this patch was never backported". Not sure how willing they are to do that, or how much effort it would take.

Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com



On May 8, 2012, at 1:46 PM, Anne Gentle wrote:

> So far the git cherry-pick command has worked for me, so I think that is the way to do it.
> 
> All I can think to do about the slippage is remind this group to request it in their reviews of master. Any other ideas?
> 
> Anne
> 
> On Tue, May 8, 2012 at 12:44 PM, Lorin Hochstein <lorin@xxxxxxxxxxxxxxxxxx> wrote:
> Now that the essex docs have been cut, how should we handle back porting doc fixes to the stable/essex branch? 
> 
> I've been proposing doc changes to master and then, once the master is approved,  cherry-picking the commit and proposing to stable/essex . Is that the way we should be doing it? If so, how do we keep doc fixes from slipping through the cracks for authors who don't realize they need to submit a second merge proposal to stable/essex?
> 
> Take care,
> 
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
> 
> 
> 
> 
> 
> 
> --
> Mailing list: https://launchpad.net/~openstack-doc-core
> Post to     : openstack-doc-core@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack-doc-core
> More help   : https://help.launchpad.net/ListHelp
> 
>