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

[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 AndrewMcIntyre:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

The comment on the change is:
feedback from Kathey on release page

------------------------------------------------------------------------------
   
    GPG is available for a variety of platforms from http://gnupg.org. PGP is a commercial product which is available from http://pgp.com.
  
+  1. For major releases, create a new branch for the release.
+ 
+   {{{svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/trunk/ https://svn.apache.org/repos/asf/db/derby/branches/{branchname}/}}}
+ 
+   There is not currently a target for bumping the version number on the trunk. You should edit release.properties by hand to bump the major/minor properties as appropriate, zero out the maint property, and ensure the beta flag is set to true. Then, from the top, run:
+ 
+   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties tools/release/maintversion.properties}}}
+   {{{cd tools/release
+ ant regex.masters}}}
+ 
+   See TODO in #8 for caveat concerning the beta flag. Don't forget to post to derby-dev requesting that a new version be added to JIRA for the next version of Derby.
+ 
-  1. Bump the third version number, finalize CHANGES, and check in the new version and test masters
+  1. Bump the third version number, adjust the beta flag, finalize CHANGES, and check in the new version and test masters
  
    There is not currently an ant target for bumping the third version number. The third and fourth parts of the version are combined into a single property, maint, where maint = (third digit * 1000000) + fourth digit. Also, if this is a major/minor (feature) release, you should remove the beta flag at this time. You should update tools/ant/properties/release.properties by hand and then run:
  
@@ -93, +105 @@

    {{{cd tools/release
  ant regex.masters}}}
  
-   TODO: the regex.masters target does not currently account for changes in the beta flag.
+   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. 'svn up' in your subversion view to bring all files in your view up to the latest revision. Otherwise, the version output by svn which is captured for the build number will be a range (e.g. 290275:320938).  
  
   1. Build the documentation, or grab a copy from the website.
  
-   The documentation needs to be included in the -bin distribution, so you will need a copy of the documentation ready when running the ant release target. Information on building the docs is located at [http://db.apache.org/derby/manuals/dita.html]. Another option is to log in to minotaur.apache.org and grab the current uploaded copy on the website, in /www/db.apache.org/derby/docs/. Tar up the correct version of the docs into your home directory (don't leave a big tarfile in /www/db.apache.org/derby/docs please!) and download it to your local machine with sftp. Untar it to a local directory, that is not inside your subversion view where you are building the release or it will be included in the -src distribution built by the release target.
+   The documentation needs to be included in the -bin distribution, so you will need a copy of the documentation ready when running the ant release target. Information on building the docs is located at [http://db.apache.org/derby/manuals/dita.html]. Another option, if your release is from the main branch or the docs have not been branched yet, is to log in to minotaur.apache.org and grab the current uploaded copy on the website, in /www/db.apache.org/derby/docs/. Tar up the correct version of the docs into your home directory (don't leave a big tarfile in /www/db.apache.org/derby/docs please!) and download it to your local machine with sftp. Untar it to a local directory, that is not inside your subversion view where you are building the release or it will be included in the -src distribution built by the release target.
  
   1. Copy packaging.tmpl to packaging.properties in tools/release and modify as necessary.
  
@@ -227, +239 @@

  
    For instructions on how to build the website, see item 3 regarding snapshots above. It is a good idea to use the previous release pages as templates, filling in the changed details as necessary. You should add a .cgi and a .html file for the release. The main thing to remember is that the .cgi file should have the same name as the .html file. Also, when you run 'svn up' on minotaur.apache.org (3e above), make sure that the new .cgi file is executable and otherwise has the correct permissions!
  
+   Note the following things when creating the release page:
+   * 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.
+   * 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}}}
+   * 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-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 minotaur.
+   * 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.
+   * Once you have committed your changes and updated the website on minotaur, you can preview your changes by following the instructions at http://www.apache.org/dev/project-site.html
+ 
   1. Deploy to Maven repository.
  
    From Jeremy Boynes:
@@ -249, +270 @@

  
   1. Tag the release in subversion.
  
-   {{{svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/{trunk_or_branchname}/ https://svn.apache.org/repos/asf/db/derby/tags/{version}/}}}
+   {{{svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/code/{trunk_or_branchname}/ https://svn.apache.org/repos/asf/db/derby/code/tags/{version}/
- 
-  1. For major releases, create a new branch for the release.
- 
-   {{{svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/trunk/ https://svn.apache.org/repos/asf/db/derby/branches/{branchname}/}}}
+ svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/docs/{trunk_or_branchname}/ https://svn.apache.org/repos/asf/db/derby/docs/tags/{version}/}}}
- 
-  1. Bump the version number to next version.
- 
-   For a bugfix release, follow the instructions in sections 4 and 5 of the Snapshot section to bump the fourth digit. There is not currently a target for bumping the version number for a feature release. You should edit release.properties by hand to bump the major/minor properties as appropriate, zero out the maint property, and set the beta flag back to true. Then, from the top, run:
- 
-   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties tools/release/maintversion.properties}}}
-   {{{cd tools/release
- ant regex.masters}}}
- 
-   See #6 for caveat concerning the beta flag. Don't forget to post to derby-dev requesting that a new version be added to JIRA for the next version of Derby.
  
   1. Update STATUS again.