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].
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.
[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
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Fri, Mar 18, 2016 at 11:23 AM, Martin Mágr <mmagr(a)redhat.com> wrote:
Greetings guys,
I think that it's time to finally start tagging packstack upstream
releases as David now needs that. This task has been in TODO list for
several releases already and was always thrown away from radar with low
priority.
I'd like us to agree on a tagging workflow. David suggested first tag
"<dmsimard> I wanted to tag 8.0.0b1", so IIUC to follow OpenStack
upstream
milestones (eg. Mitaka beta1 -> 8.0.0b1 ?). Has anybody something against
that scheme?
What should be the first tag in stable/liberty?
Regards,
Martin