[Beehive Wiki] Update of "For Beehive Developers" by EddieOneil

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Beehive Wiki" for change notification.

The following page has been changed by EddieOneil:
http://wiki.apache.org/beehive/For_Beehive_Developers

The comment on the change is:
Add instructions for creating a distribution

------------------------------------------------------------------------------
  
  If you're running Windows, you can get the {{{patch}}} command as part of Cygwin (http://www.cygwin.com/).  The MKS 6.1 {{{patch}}} command does ''not'' work for this -- if you use MKS, download Cygwin, make sure it's on your path, and disable the MKS patch.exe.
  
+ = Creating a Beehive Distribution =
+ 
+ Creating a Beehive distribution is reasonably easy and consists of a couple of basic steps:
+ 
+ == Building and testing the distribution archives ==
+  1. Update the Beehive documentation to replace these tokens "Beehive SVN" with "Beehive <version-number>"
+  1. {{{cd trunk/}}}
+  1. Run this command to build and test the distribution: {{{ant -f nightly.xml run -Dbeehive.version=<version-number>}}}
+  1. Checksum and sign the release
+  1. Create these sub-directories: {{{/www/www.apache.org/dist/beehive/<version-number>/(binaries|source)}}}
+  1. FTP the distribution's {{{.zip}}}, {{{.tar.gz}}}, {{{.asc}}}, and {{{.md5}}} files to an ASF server
+  1. Copy the appropriate resources to the {{{<version-number>/(binaries|source)}}} sub-directories
+ 
+ Before FTP-ing to the ASF servers, be sure that **all** of the distribution's tests pass by manually verifying a 100% test pass rate in the generated test reports.
+ 
+ == Linking the distribution the website ==
+  1. Link the documentation for the release to {{{beehive/site/src/documentation/content/xdocs/documentation.xml}}} 
+  1. Copy an existing download .cgi script and rename it to {{{release-<version-number>.cgi}}}
+  1. Copy an existing download .html file and rename it to {{{release-<version-number>.html}}}
+  1. Link the download for the release to {{{beehive/site/src/documentation/content/xdocs/downloads.xml}}}.  Be sure to link to the {{{.cgi}}} script
+  1. Replace the version number in {{{release-<version-number>.html}}} with the new <version-number> token
+  1. Add {{{releases/release-<version-number>.html}}} to {{{site/src/documentation/conf/cli.xconf}}}
+  1. Run {{{cd beehive/site && ant clean build site.stage}}}
+  1. Copy {{{$FORREST_HOME/main/site/releases/release-<version-number>.html}}} to {{{beehive/site/www/releases}}} to work around a very unfortunate Forrest bug
+  1. Replace the download HTML <form> in {{{www/releases/release-<version-number>.html}}} with the <form> templated for the ASF CGI download script from {{{src/documentation/content/xdocs/releases/release-<version-number>.html}}}.  This is needed because Forrest mangles the tokens that are replaced when the .html file is used as a template from the download's .cgi script
+  1. Commit the site changes to SVN
+  1. SSH to an ASF server and run {{{cd /www/beehive.apache.org && svn update}}}
+ 
+ While this seems like lots of steps, updating the website doesn't take that long.  The worst part is working around the Forrest mismatch with the .cgi scripts!
+