[Rdo-list] Packstack tagging
Ivan Chavero
ichavero at redhat.com
Fri Mar 18 19:46:11 UTC 2016
>
> I'd go indeed with the OpenStack cycle milestones, so for Newton:
>
> <master> .. 9.0.0b1 <-- milestone1
> 9.0.0b1 .. 9.0.0b2 <--- milestone2
> 9.0.0b2 .. 9.0.0b3 <--- milestone3
> 9.0.0b3 .. 9.0.0rc1 <--- rc1
> 9.0.0rc1 .. 9.0.0rcN <--- rcN (if necessary)
> 9.0.0rcN .. 9.0.0 <--- release
>
This sounds good
>
> On Fri, Mar 18, 2016 at 11:38 AM, David Moreau Simard <dms at redhat.com> wrote:
> > For context, when working on release notes for Packstack with Reno I
> > noticed that it relied on git tags for providing version-based release
> > notes [1].
> >
> >> Notes are immutable in that for a given git hash/tag the release notes
> >> will be the same. Tagging a commit will change the version description
> >> but that is all.
> >
> > Since Packstack doesn't have any tags right now, Reno builds the
> > following notes:
> > ---
> > =============
> > Release Notes
> > =============
> >
> > 0.0.0
> > =====
> >
> > Release notes for Packstack are now managed through Reno.
> > ---
> >
> > Reno allows release notes to be fit between two tags appropriately,
> > i.e, like the Nova ones [2].
> > Tagging is also relied on by PBR when generating version numbers and
> > I'd like to see Packstack transition it's setup to PBR eventually [3].
we can also do this i don't know very much about PBR, i'll check it out
> > Packstack is known as 8.0.0 for Mitaka already, so let's just start
> > with that IMO.
> > We can start at rc1 instead of b1 at this point I guess - the
> > stable/mitaka branch is already cut.
> > The proposed scheme also fits puppet module release tags [4].
> >
> > I don't know if a tag for Liberty is necessary, we can probably start
> > for Mitaka.
we should tag liberty also
> > [1]: http://docs.openstack.org/developer/reno/design.html
> > [2]: http://docs.openstack.org/releasenotes/nova/unreleased.html
> > [3]: https://bugs.launchpad.net/packstack/+bug/1559150
> > [4]: https://github.com/openstack/puppet-nova/releases
Cheers,
Ivan
More information about the dev
mailing list