Description of problem: These BZs are in status NEW or ASSIGNED and are in bug fixes section of release notes: https://bugzilla.redhat.com/show_bug.cgi?id=1117447 https://bugzilla.redhat.com/show_bug.cgi?id=1118373 Version-Release number of selected component (if applicable):
RN Revision 6.3.0-14
A new version of the Release Notes is available for review at: https://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/6.3.0_Release_Notes/index.html (ensure you're reviewing version 6.3.0-17) Brew task: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=7735113
I noticed that two bugzillas representing the same issue are now in the release notes: 1114699 and 1117447 represent the same issue, but are targeted for a different EAP version. One of them should be removed from the release notes.
I am not sure of the *best* method of excluding one of these BZ from the JBoss EAP 6.3.0 Release Notes document. Rather than modifying flags and/or fields now, I will have the person collating the Release Notes manually exclude one of these, most likely BZ1114699.
Set the 'requires_doc_text' flag to '-' in Bug 1114699 because it is targeted for 6.4 and duplicates Bug 1117447
As above, 1117447 and 1118373 are now in Known issues, and 1114699 is excluded. Ready for review (Revision 6.3.0-18): https://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/6.3.0_Release_Notes/index.html
verified, RN Revision 6.3.0-18