Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: derby-commits@db.apache.org
Date: Fri, 18 May 2007 14:16:36 -0000
Message-ID: <20070518141636.6578.40269@eos.apache.org>
Subject: [Db-derby Wiki] Update of "ReleaseNoteProcess" by RichardHillegas

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

------------------------------------------------------------------------------
  ## page was renamed from DerbyReleaseNoteProcess
+ 
+ '''Table of Contents'''
+ [[TableOfContents(3)]]
+ 
+ == Writing a Release Note ==
+ 
  Good release notes are essential for users as they upgrade from one release to the next. Here's the procedure the Derby team uses to maintain useful release notes:
  
   * For JIRAs which need a release note, you should turn on the "Release Note Needed" flag and attach a file called "releaseNote.html".
@@ -9, +15 @@

  
  Some additional discussion regarding this process can be found in DERBY-2570.
  
+ == Generating the Release Documentation ==
+ 
+ As part of producing a Derby release, the Release Manager creates RELEASE-NOTES.html, a web page which lives in the top directory of the branch codeline, next to the STATUS and CHANGES files. This file ships with the release distributions and is also incorporated into the release download page on the Apache website. RELEASE-NOTES.html describes Derby's key capabilities and it summarizes the delta between the new release and some previous release--usually the last release produced by the community. The Issues section of RELEASE-NOTES.html includes the releaseNotes.html files which were attached to significant JIRAs.
+ 
+ To generate RELEASE-NOTES.html, the Release Manager first prepares the environment:
+ 
+  * '''Build''' - Builds the branch codeline in order to compile the 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 two xml JIRA reports:
+    * fixedBugsList.xml - This is the list of issues addressed by the release
+    * releaseNotes.xml - This is the list of issues bearing detailed releaseNotes.html explanations.
+ 
+ Then the Release Manager builds RELEASE-NOTES.html:
+ 
+  * '''relnotes.src.reports''' - In ant.properties, this variable should point at the directory which holds the two xml JIRA reports.
+  * '''cd''' - Change directory to tools/release.
+  * '''ant''' - Run ant like so: "ant genrelnotes"
+ 
+ Please note that the Release Manager should run the JIRA reports freshly just before typing "ant genrelnotes". This is because, during the release period, new issues may be fixed and included in the release and the text for individual release notes may be improved. Stale reports overlook the new issues and improved notes.
+