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 KatheyMarsden:
http://wiki.apache.org/db-derby/ReleaseNoteProcess?action=diff&rev1=20&rev2=21

   * '''Build''' - Builds the branch codeline in order to compile the [[https://svn.apache.org/repos/asf/db/derby/code/trunk/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java|ReleaseNotesGenerator]] program.
   * '''Summarize''' - Fills in a summary of the release. This involves filling in the top level `releaseSummary.xml` file, based on the instructions in its template file tools/release/templates/releaseSummaryTemplate.xml.
   * '''Report''' - Generates a JIRA report:
-    * `fixedBugsList.xml` - This is the list of issues addressed by the release. To generate this file you need to save a filter for the appropriate search in Jira. You will typically need to create a new filter for each release. The criteria for `fixedBugsList.xml` will be something like fixversion=<branch or all release candidate versions>, resolution=fixed and type=bug. Save this report to disk. In some browsers you can then right-click this link and select "Save link as..." from the resulting menu. Make sure you change the name to `fixedBugsList.xml` and save it in the location pointed to by `relnotes.src.reports` as described below.  
+    * To generate the release notes  you need to save a filter for the appropriate search in Jira. You will typically need to create a new filter for each release. The criteria for will be something like fixversion=<branch or all release candidate versions>, resolution=fixed and type=bug. This filter will be identified in the ant arguments to generate `RELEASE-NOTES.html`
  
  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.