[Db-derby Wiki] Update of "DerbySnapshotOrRelease" by MyrnavanLunteren

[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 following page has been changed by MyrnavanLunteren:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

------------------------------------------------------------------------------
  
   1. Fix the bugs, update STATUS and CHANGES as needed
  
-   Get to work! Add features, fix bugs, and update STATUS and CHANGES as you go. The wiki is nice, as are personal webpages, but STATUS and CHANGES are the designated place for Apache projects to keep their current status. Apache members and committers expect to be able to grab the STATUS file from the code tree to determine the current status of the project. It's a nice thing to keep the STATUS file on branches up to date with the current status of the branch.
+   Get to work! Add features, fix bugs, and update STATUS as you go. The wiki is nice, as are personal webpages, but STATUS is the designated place for Apache projects to keep their current status. Apache members and committers expect to be able to grab the STATUS file from the code tree to determine the current status of the project. It's a nice thing to keep the STATUS file on branches up to date with the current status of the branch. The other essential document is a document describing the changes. Derby branches up to 10.2 included a file 'CHANGES' for that purpose; 10.3 branch and trunk have a RELEASE_NOTES.html checked in. RELEASE_NOTES.html is generated using the generator in <10.3 branch and up/trunk>/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java.
  
   1. Drive the bug list to zero.
  
-   As the list of remaining bugs in JIRA approaches zero, be sure to mark their status properly in JIRA. Mark blocker and critical bugs as such so that others can see the status at a glance. Move non-showstopper bugs out to future releases if it appears they will not be fixed for this release.
+   As the list of remaining bugs in JIRA approaches zero, be sure to mark their status properly in JIRA. Mark blocker and critical bugs as such so that others can see the status at a glance. Move non-showstopper bugs out to future releases if it appears they will not be fixed for this release. 
+ 
+  1. Drive the creation of release notes.
+   The release note generator expects files called 'ReleaseNote.html' for each item marked that is:
+     - resolved to 'Fixed'
+     - fixed in the release under study but not in the previous release
+     - marked with 'Existing Application Impact' or 'Release Note Needed'.
  
   1. Make sure your public PGP/GPG key is in the KEYS file 
  
@@ -119, +125 @@

  
    TODO: the regex.masters target does not currently account for changes in the beta flag. If you are creating the first release off of a new branch, do not forget to set the beta flag in tools/ant/properties/release.properties to false.
  
- 
-   Finalize any comments added to CHANGES, so that you do not need to alter the file before you are ready to build. Check in the updated files.  
  
   1. Generate RELEASE_NOTES.html in the branch and check it into the svn repository.