Re: [openstack-dev] [neutron] [release] misleading release notes

2017-02-02 Thread Dean Troyer
On Thu, Feb 2, 2017 at 7:42 AM, Doug Hellmann wrote: > As long as the edit happens on the branch where the note should appear, > it should be fine. Excellent! Just tried it and it does, thanks. I think https://review.openstack.org/427842 is doing what you intend, I can

Re: [openstack-dev] [neutron] [release] misleading release notes

2017-02-02 Thread Doug Hellmann
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. 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 > >

Re: [openstack-dev] [neutron] [release] misleading release notes

2017-02-02 Thread Doug Hellmann
Excerpts from Armando M.'s message of 2017-02-01 18:13:46 -0800: > Hi, > > There is something puzzling about release notes. I don't see 8.0.0 [1], and > it looks like features released in Mitaka are being advertised as Newton > features [2]. For instance, [3] 'Agent availability zones' shows as a

Re: [openstack-dev] [neutron] [release] misleading release notes

2017-02-01 Thread Dean Troyer
On Wed, Feb 1, 2017 at 8:13 PM, Armando M. 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

[openstack-dev] [neutron] [release] misleading release notes

2017-02-01 Thread Armando M.
Hi, There is something puzzling about release notes. I don't see 8.0.0 [1], and it looks like features released in Mitaka are being advertised as Newton features [2]. For instance, [3] 'Agent availability zones' shows as a Newton feature when I am pretty positive that it went in Mitaka [4]. I