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 RichardHillegas
Date Tue, 19 Aug 2008 14:00:08 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 RichardHillegas:
http://wiki.apache.org/db-derby/ReleaseNoteProcess

------------------------------------------------------------------------------
     * `fixedBugsList.xml` - This is the list of issues addressed by the release
     * `releaseNotesList.xml` - This is the list of issues bearing detailed releaseNotes.html
explanations.
   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=<branch or all release candidate versions>, resolution=fixed
and type=bug. For `releaseNotesList.xml` you also need to check the 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 and 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
below.
+  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 and 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
below. Each of these reports begins with a DOCTYPE declaration. These declarations point at
a DTD which is not present on your machine; those references choke the release notes generator,
so remove the DOCTYPE declarations.
  
  Then the Release Manager builds `RELEASE-NOTES.html`:
  

Mime
View raw message