[openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

Doug Hellmann doug at doughellmann.com
Mon Nov 9 14:22:41 UTC 2015


Excerpts from Andreas Jaeger's message of 2015-11-07 16:42:40 +0100:
> On 11/03/2015 08:46 PM, Doug Hellmann wrote:
> > [...]
> > We are ready to start rolling out Reno for use with Liberty stable
> > branch releases and in master for the Mitaka release. We need the
> > release liaisons to create and merge a few patches for each project
> > between now and the Mitaka-1 milestone.
> >
> > 1. We need one patch to the master branch of the project to add the
> >     instructions for publishing the notes as part of the project
> >     sphinx documentation build.  An example patch for Glance is in
> >     [2].
> >
> > 2. We need another patch to the stable/liberty branch of the project
> >     to set up Reno and introduce the first release note for that
> >     series. An example patch for Glance is in [3].
>  > [...]
> 
> What shall we do with projects that do not have a stable/liberty? For 
> example openstack-doc-tools does not have one and we hope we don't need one?

There are 2 ways to handle projects without the stable branch. You
could simply write the notes in a single rst file and skip using
reno. The point of reno is to make backporting notes easier, but
if you aren't doing backports that's not necessary.

If you want to use reno, just set up a page that lists the releases
from the master branch.

> 
> Does the following look ok?
> https://review.openstack.org/242748

That's a good start. You could replace the contents of
releasenotes/source/index.rst with something like

  .. release-notes::
     :branch: origin/master

> 
> Also, what do you think of adding this to openstack-manuals? We do not 
> tag releases for the manuals but release continously. Will the tools 
> work fine here?

reno depends on the tags to know how to organize the notes. If you're
not tagging versions of the manuals, you won't get much benefit from it.
We should talk about alternative ways to build a good changelog for the
manuals, if you want to try to automate some of that.

Doug

> 
> Andreas



More information about the OpenStack-dev mailing list