[openstack-dev] [release][reno][infra] merging tags between branches is confusing our release notes

Doug Hellmann doug at doughellmann.com
Fri Jun 24 17:59:04 UTC 2016

Excerpts from Doug Hellmann's message of 2016-06-08 14:13:44 -0400:
> tl;dr: The switch from pre-versioning to post-versioning means that
> sometimes master appears to be older than stable/$previous, so we
> merge "final" tags from stable/$previous into master to make up for
> it. This introduces versions into the history of master that aren't
> *really* there, but git sees them and so does reno. That, in turn,
> means that the release notes generated from master may place some
> notes in the wrong version, suggesting that something happened
> sooner than it did. I propose that we stop merging tags, and instead
> introduce a new tag on master after we create a branch to ensure
> that the version number there is always higher than stable/$previous.

The change to implement this has merged [1].


[1] https://review.openstack.org/#/c/333421/

More information about the OpenStack-dev mailing list