db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "ReleaseNoteProcess" by DyreTjeldvoll
Date Tue, 18 Mar 2008 09:47:41 GMT
Dear Wiki user,

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

The following page has been changed by DyreTjeldvoll:

   * Before attaching your release note, make sure that the release processes can digest it.
Run the lint tool, !ReleaseNoteReader, on your note as follows: "java org.apache.derbyBuild.!ReleaseNoteReader
RELEASE_NOTE_FILE" where RELEASE_NOTE_FILE is the name of the file which holds your release
   * As you improve the wording of your release note, you simply attach a new version of releaseNote.html.
The release documentation will include the last version of the release note.
- Some additional discussion regarding this process can be found in DERBY-2570.
+ Some additional discussion regarding this process can be found in [https://issues.apache.org/jira/browse/DERBY-2570
  == Generating the Release Documentation ==
@@ -27, +27 @@

   * '''Report''' - Generates two xml JIRA reports:
     * fixedBugsList.xml - This is the list of issues addressed by the release
     * releaseNotesList.xml - This is the list of issues bearing detailed releaseNotes.html
+  To generate these two files you need to use the appropriate search or filter in Jira. You
will typically need to create a new filter for each release. The criteria for `fixedBugsList.xml`
will be something like fixversion=<release candidate> and resolution=fixed and type=bug.
For `releaseNotesList.xml` you also need to check release note checkbox.
+  After running the search in Jira the you will see a link called "XML" above the search
results. In some browsers you can then right-click this link a select 'Save link as..." from
the resulting menu. Make sure you change the name (to `fixedBugsList.xml` or `releaseNotesList.xml`
as appropriate), and save it in the location pointed to by `relnotes.src.reports` as described
  Then the Release Manager builds RELEASE-NOTES.html:

View raw message