release notes have older entries

[YAMAMOTO Takashi]

for some reasons ocata release notes have older entries.
https://docs.openstack.org/releasenotes/networking-midonet/ocata.html

[YAMAMOTO Takashi (yamamoto)]

bug 1708560 is similar

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/491952

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/491953

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/491957

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/491952
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=bb795ca63f41e674ba4a27043dee872edb0edca7
Submitter: Jenkins
Branch: master

commit bb795ca63f41e674ba4a27043dee872edb0edca7
Author: YAMAMOTO Takashi <email address hidden>
Date: Wed Aug 9 09:03:53 2017 +0900

    releasenotes: Ignore older entries in Pike release notes

    I somehow had a wrong assumption that reno only includes entries
    added during the cycle. However, actually it also includes ones
    modified in the cycle as well, as shown in the "reno list" output. [2]
    I guess it would be useful to add an option to reno itself,
    but for now, explicitly exclude entries for older releases,
    following the similar change in horizon. [1]

    [1] Iafe8365dca2a6ef963d7c459dab486975da939bc
    [2] http://paste.openstack.org/show/617859/

    Partial-Bug: #1682776
    Change-Id: I8667f6432b158fe6b51483e3ae62d9c1ecd128e7

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/491953
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=48d4b0caba111cddbc3f2debe0d01a0184f68b95
Submitter: Jenkins
Branch: master

commit 48d4b0caba111cddbc3f2debe0d01a0184f68b95
Author: YAMAMOTO Takashi <email address hidden>
Date: Wed Aug 9 09:29:34 2017 +0900

    releasenotes: Ignore older entries in Ocata release notes

    I somehow had a wrong assumption that reno only includes entries
    added during the cycle. However, actually it also includes ones
    modified in the cycle as well, as shown in the "reno list" output. [2]
    I guess it would be useful to add an option to reno itself,
    but for now, explicitly exclude entries for older releases,
    following the similar change in horizon. [1]

    [1] Iafe8365dca2a6ef963d7c459dab486975da939bc
    [2] http://paste.openstack.org/show/617860/

    Closes-Bug: #1682776
    Change-Id: I2999862f530fb27f767141f092133bd7bd489644

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/491957
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=4f70009374ff7c49bfbe517a43721e6ede5ae6d2
Submitter: Jenkins
Branch: master

commit 4f70009374ff7c49bfbe517a43721e6ede5ae6d2
Author: YAMAMOTO Takashi <email address hidden>
Date: Wed Aug 9 10:12:47 2017 +0900

    doc: Stop using reno.sphinxext

    Because we don't want to maintain ignore-notes list in
    multiple places. Just have a docs.o.o reference instead.

    Partial-Bug: #1682776
    Change-Id: I20d9a82185d87ee81711a44921907cd28044e65e

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/networking-midonet 6.0.0.0b1 development milestone.