[openstack-dev] Thoughts on ReleaseNoteImpact git commit message tag

Soren Hansen soren at linux2go.dk
Wed Jul 8 10:42:48 UTC 2015

Putting release notes in the git repo so that they simply will get
merged along with the corresponding code seems like a no-brainer. What
am I missing?

Soren Hansen             | http://linux2go.dk/
Ubuntu Developer         | http://www.ubuntu.com/
OpenStack Developer      | http://www.openstack.org/

2015-07-08 12:13 GMT+02:00 Thierry Carrez <thierry at openstack.org>:
> Matt Riedemann wrote:
>> [...]
>> So we kicked around the idea of a ReleaseNoteImpact tag so that we can
>> search for those at the end of the release in addition to UpgradeImpact.
> I like the idea -- could be a commit message tag or waiting for the wiki
> update to approve (as Dan suggested), I think both would work.
> As a sidenote, we are reconsidering stable release notes with the plan
> we came up with for stable branches[1] (we decided to switch to
> versioning and releasing every stable branch commit). To produce valid
> release notes for any of those, we need to autogenerate them and ship
> them as part of the tarball.
> That means for stable branches we'll need a way to specify release notes
> snippets in the git repository itself. Something like a header in commit
> messages that would get added as a bullet point to the auto-generated
> release notes in the tarball.
> We still need to discuss the details, but maybe whatever we come up with
> for stable branches could be reusable for master branches in the future.
> [1] http://lists.openstack.org/pipermail/openstack-dev/2015-July/068400.html
> --
> Thierry Carrez (ttx)
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list