Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Adding instructions on adding one's public key to KEYS file.

...

After that, four files (tar/gz & .asc for them) will be in the weblogger-assembly/target directory.

4. Upload files for review

Upload to your home directory the files on people.apache.org, for example for RC1 you might put them here:

Code Block
   /home/<username>/public_html/rc1

...

3. Create release for Java EE

The commands below will create the Roller for Java EE release bundle in ZIP and Gzipped TAR formats and the ASCii signature files:

Code Block
   ./build-javaee-release.sh
   ./sign-javaee-release.sh

After that, four files (tar/gz & .asc for them) will be in the weblogger-assembly/target directory. 

If you haven't already, you will also need to upload your public key to Roller's KEYS file in SVN, as well as the KEYS file in the Roller distribution folder (they are not presently the same.)  This has to be done only once for Roller no matter how many releases you make.  First use "gpg --list-keys" to determine the 8 character key ID for your key, and then make an ASCII armored key for it and add it to the MIT public key server.  For the SVN KEYS file, as it is in a top-level directory that would result in downloading tons of files if you tried a full checkout, do an empty checkout of the folder and then an individual svn update to get just the KEYS file, add your public key to it using the instructions at the top of the file, and then commit the KEYS file back:

Code Block
svn co https://svn.apache.org/repos/asf/roller --depth=empty
cd roller
svn update KEYS
(add public key to KEYS)
svn commit KEYS -m "Added my key to KEYS file."

For the Roller distribution KEYS file, do an ssh to <your apache user id>@people.apache.org, navigate to the /dist/roller folder, and use vi or another command line tool to add your KEY to that file.  (For vi, go to the end of the file by entering a capital G followed by a small o to enter edit mode, then paste your key in, followed by an Escape key and a :wq to save the file.)

4. Check In Version changes

Do an SVN commit of the changes you did in Step #1.  Then, add a release candidate tag using the svn copy command, for example:

...