[Db-derby Wiki] Update of "ReleaseNoteProcess" by RichardHillegas

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The "ReleaseNoteProcess" page has been changed by RichardHillegas:
https://wiki.apache.org/db-derby/ReleaseNoteProcess?action=diff&rev1=23&rev2=24

Comment:
Add link to instructions on how to build a fixedBugsList.txt file.

  Note: 
  For versions older than 10.8, these instructions may be different. For instance, at one point, generating the release notes involves using the class java/build/org/apache/derbyBuild/ReportParser. You needed to tweak this report because the shape of JIRA reports changes significantly between Derby releases. Fortunately, it is easy to write one of these parsers. See !ReportParser$April_2010 as an example. For more information on producing this report for older branches, see the header comment on !ReportParser$April_2010 on a branch that has it.
  
+ From 10.8 through 10.14.1.1, the release notes generator used a SOAP api in order to extract the list of fixed bugs. This broke after JIRA was upgraded to a modern version which no longer supports the SOAP api. Now you need to manually construct a list of fixed bugs called fixedBugsList.txt. Instructions for making that file can be found at the FixedBugsList wiki page.
+ 
  Then the Release Manager builds `RELEASE-NOTES.html`:
  
  {{{
@@ -43, +45 @@

      -Djira.user=<jira user name>
      -Djira.password=<password for that user>
      -Drelease.version=<version of the release in JIRA>
-     -Djira.filter.id=NNNNNNN (the JIRA filter ID to select those issues fixed in this release)
     genrelnotes
  }}}
  
  If you forget or have not set any of these settings, the release notes build will fail and you will be informed of which element you've missed.
- 
- By default the tool will use JQL to query JIRA. If the query fails for some reason, you can create you own custom filter in JIRA and point the tool at it by specifying `jira.filter.id`. To find the filter id, save the JIRA query as a filter, and then use the number following the id in the url window when the search has been issued.
  
  You can also specify `reportDisqualifications=true` to see the issues that are disqualified. Currently, the only cause for a disqualification is that the fix for an issue has already been included in a previous version in the ancestry chain.