[Db-derby Wiki] Update of "TmpDerbySnapshotOrRelease" 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/TmpDerbySnapshotOrRelease

The comment on the change is:
catching up on changes to DerbySnapshotOrRelease before continuing to stir

------------------------------------------------------------------------------
    Note the following things when creating the release page:
    * Be sure to specify that the src.tar.gz requires gnu tar to unravel (because of our usage of ant tar to create this, using longfile=gnu for handling long filenames).
    * Forrest will not copy the release .cgi script over unless you make a link to it from another page. Add the link to derby_downloads.html before building.
+   * Remove all square brackets [] from the release notes page. When the cgi machinery sees square brackets, it truncates the release page.
    * Make sure that the .cgi script is made executable by setting svn:executable on it with {{{svn propset 
  svn:executable ON release-10.1.2.1.cgi}}}. Be sure to do this for both the precursor version you created in src/documentation/content/xdocs/releases and for the generated copy which forrest builds into build/site/releases.
    * In order for the release HTML file to be pulled into the build, it is necessary to add a line to the <uris> section of src/documentation/conf/cli.xconf. Near line 310 of that file, add: <uri type="append" src="releases/release-10.1.2.1.html"/> (with the correct version for your release)
+   * Due to [http://issues.apache.org/jira/browse/FOR-555]FOR-555, the HTML comments which constitute the form template into which the mirrors.cgi script splices in the mirror information will be removed by Forrest. It is necessary to add these comments back in to the release page before committing or letting the site go live on people.apache.org.
    * Due to [http://issues.apache.org/jira/browse/FOR-480]FOR-480, the release page will be built into your $FORREST_HOME/main/site directory.
-   * Due to [http://issues.apache.org/jira/browse/FOR-555]FOR-555, the HTML comments which constitute the form template into which the mirrors.cgi script splices in the mirror information will be removed by Forrest. It is necessary to add these comments back in to the release page before committing or letting the site go live on people.apache.org.
+   * Svn delete the cgi script for the previous release. Also, edit its release page to remove the cgi boilerplate and convert the distribution links from mirror references to ordinary links. This means removing the [preferred] tags. To see what this should look like, look at the release page for an even older release.
    * Subversion may report some files as changed which should be static. Revert anything in build/site/skin or build/site/papers before committing your website changes ([http://db.apache.org/derby/papers/derby_web.html#odd_diffs see the explanation]).
    * Once you have committed your changes and updated the website on people, you can review your changes by following the instructions at http://www.apache.org/dev/project-site.html
  
@@ -473, +475 @@

  
   1. Update STATUS again.
  
-   Update STATUS to reflect that the release has occurred. Check in the new file. You're done!
+   Update STATUS to reflect that the release has occurred. Check in the new file. 
+ 
+  1. Update the News section of the website.
+ 
+   Update the News section at the bottom of the front page of the Derby website. Add the announcement mail to the top of the news items at http://db.apache.org/derby/index.html#News 
+ 
+  1. Update JIRA versions and merge development versions into released version.
+ 
+   Mark the release id as a released version in JIRA. To do this, go to the Administration page, select Derby, then click the Manage versions link on the bottom right. Click the Release link next to the version id of the release and add the release date. In addition, you may need to create a new version id for the next release vehicle on the branch. The older development versions used for tracking changes between releases are no longer needed, and old versions should be merged into the release version. E.g. for the 10.3.1.4 release, 10.3.0.0, 10.3.1.0, 10.3.1.1, 10.3.1.2, and 10.3.1.3 need to be merged into the released 10.3.1.4. Click the Merge button next to the oldest release. Select all the versions in the list on the right to merge and then the released version to merge to on the left (in the example above, this would be 10.3.1.4), and click the Merge button and confirm the merge.
+ 
+ You're done!
+ 
  
  == Snapshots ==
   1. Update CHANGES.