[Openstack] [RFC] Stable branch

Mark McLoughlin markmc at redhat.com
Mon Oct 17 11:10:36 UTC 2011


Hi James,

On Fri, 2011-10-14 at 12:43 -0400, James E. Blair wrote:
> Mark McLoughlin <markmc at redhat.com> writes:
> >> > Each project will have a branch named after the previous release. For
> >> > example, the stable branch for the diablo release will be simply
> >> > called 'diablo'.
> >> 
> >> Sounds good.  I'll create branches in gerrit named 'diablo' branching
> >> from the commit with the 2011.3 tag.  I think we can update the release
> >> management process to incorporate this step for essex.
> >
> > Cool stuff.
> 
> It turns out that if we name the maintenance branches something we can
> match a regex against, then we can configure Gerrit to give the
> openstack-stable-maint group approval access to all maintenance branches
> with just one ACL.  Otherwise we would have to remember to add a new ACL
> when be branch essex.  Would you object to calling the branches
> "maint-*", e.g., "maint-diablo", "maint-essex", etc?

Cool stuff. I don't care much about the name, but I'd call it
diablo-stable

> > Does the current diablo branch for Nova pass all tests on jenkins?
> > Perhaps we should start by bypassing jenkins and pushing these commits
> > directly to the branch:
> >
> >   $> $ git log --oneline origin/diablo..d6137fb
> >   d6137fb Fix outstanding pep8 errors for a clean trunk.
> >   b0e855e Removing old code that snuck back in
> >   6503923 Made jenkins email pruning more resilient.
> >   ba68a78 Don't use GitPython for authors check
> >   3a63bd5 Add tools/rfc.sh from master
> 
> Sounds reasonable.

Great. Can we pull the trigger on this then? Once we got this much set
up, I'll start pushing the rest of the patches through gerrit

Cheers,
Mark.





More information about the Openstack mailing list