[openstack-dev] [neutron] [release] misleading release notes
doug at doughellmann.com
Thu Feb 2 13:42:04 UTC 2017
Excerpts from Dean Troyer's message of 2017-02-01 22:41:46 -0600:
> On Wed, Feb 1, 2017 at 8:13 PM, Armando M. <armamig at gmail.com> wrote:
> > I suspect what happens is that someone revises the content at a later date
> > and reno associated the last timestamp of the release note with release
> > where the change has been made?
> I do believe this is the case, reno puts a note in the release that it
> find it in, thus editing notes after branching is going to give you
> the result you so not want.
> I've made a point to do one last relnote cleanup pass before releases
> to catch the errors/typos that have slipped through, but OSC doesn't
> have near the volume of commits or notes that many projects have...
As long as the edit happens on the branch where the note should appear,
it should be fine.
More information about the OpenStack-dev