release note entries included for wrong release

Bug #1682796 reported by YAMAMOTO Takashi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Won't Fix
Undecided
Unassigned
reno
Fix Released
Undecided
Unassigned

Bug Description

ocata release note [1] has an entry for mitaka. [2]
it seems the file has been updated in ocata cycle. [3]

[1] https://docs.openstack.org/releasenotes/neutron/ocata.html

[2] hyperv-neutron-agent-decomposition-ae6a052aeb48c6ac.yaml
    ("Hyper-V Neutron Agent has been fully decomposed from Neutron.")

[3] Iec8494b40fed2d427c1edf4609f8b3dd8c770dce

description: updated
summary: - misleading release note
+ release note entries included for wrong release
Changed in neutron:
status: New → Confirmed
Changed in reno:
status: New → Confirmed
Sapna Jadhav (sapana45)
Changed in neutron:
assignee: nobody → Sapana Jadhav (sapana45)
Revision history for this message
Sapna Jadhav (sapana45) wrote :

Do we need to remove "The Hyper-V Neutron Agent has been fully decomposed from Neutron." line from hyperv-neutron-agent-decomposition-ae6a052aeb48c6ac.yaml of neutron stable/ocata ?
As i am new contributer please correct me.
Thanks

Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

Sapana,

removing the line from the file is not a good idea given the way reno scans entries.
i guess you can add ignore-notes for ocata.rst instead.

there might be more entries which need to be fixed besides the hyperv one mentioned in the description of this bug. i haven't checked.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

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

Changed in neutron:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to reno (master)

Reviewed: https://review.openstack.org/518961
Committed: https://git.openstack.org/cgit/openstack/reno/commit/?id=bcc65c9e846c829158671ccfbcd0308284f2092a
Submitter: Zuul
Branch: master

commit bcc65c9e846c829158671ccfbcd0308284f2092a
Author: Doug Hellmann <email address hidden>
Date: Thu Nov 9 20:08:07 2017 +1100

    ignore changes until the file is added within the scanned range

    Ignore changes to a note file until the scanner encounters the git
    operation that adds the file. This ensures that if a file is modified
    on master when it should be modified on another branch the note is not
    incorporated into the notes for the next release from master.

    Change-Id: I4e41c482695e93ebb5a73866c432636201a7534f
    Fixes-Bug: #1682796
    Signed-off-by: Doug Hellmann <email address hidden>

Changed in reno:
status: Confirmed → Fix Released
Sapna Jadhav (sapana45)
Changed in neutron:
assignee: Sapana Jadhav (sapana45) → nobody
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by "Rodolfo Alonso <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/neutron/+/519073
Reason: It's been 4 years, feel free to restore the patch if needed.

Changed in neutron:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.