...
Releases heretofore have been done on Windows (both US locale and Japan locale), and thus we feel that the release process is fairly robust for that platform. Batch scripts have been created that ease the process mightily. On Linux there has been no such development; if you like, you can be the first release engineer who wants to port the scriptsare also scripts which have been used for one release.
Branches and tags
For any release, there should be a release branch. In the past, this branch has been created by the appropriate "svn copy" command from trunk. For example:
...
NOTE: In order to proceed, you MUST have svn 1.7 or higher installed! The ant build scripts require this in order to be able to apply patches on Windows platforms. On Windows, you You will also need GnuPG installed (from http://www.gnupg.org/download/), and have your signing key created and installed (read this: http://www.apache.org/dev/release-signing). Also needed is the utility "pscp.exe", and a properly configured public/private key signon to people.apache.org (which is required to upload artifacts; read here how to set that up: https://www.debian-administration.org/article/530/SSH_with_authentication_key_instead_of_password).
...
svn co https://svn.apache.org/repos/asf/manifoldcf/release-0.6-branch myworkarea
Then, check out the Windows release scripts also:
svn co https://svn.apache.org/repos/asf/manifoldcf/release-scripts
...
