THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Check out the Apache Roller source code from the appropriate branch. Within the pom files, update the Roller version number to what you will be releasing (for example, 5.0.4-SNAPSHOT to 5.0.4). Update the version within the sign*.sh file(s) in the root folder to that version as well.
2.
...
(5.0.x only)
...
Create release for Tomcat and Java EE
The commands below will create the Roller for Tomcat release bundle in ZIP and Gzipped TAR formats and the ASCii signature files:
...
Once done, move the six files (tar/gz/source & .asc for them) outside of weblogger-assembly/target folder (otherwise, those files will be lost in the Java EE build in the next step).
3. Create release for Java EE (5.0.x only)
The commands below will create the Roller for Java EE release bundle in ZIP and Gzipped TAR formats and the ASCii signature files:
...
After that, four files (tar/gz & .asc for them) will be in the weblogger-assembly/target directory.
3. (5.1.x only) Create single release
From the Roller root folder, run mvn clean install. Next, navigate to the assembly-release folder and run mvn clean install again. Then run sign-release.sh. In the assembly-release/target folder of the latter you'll have a total of eight files that need uploading: two ZIP and two tar.gz files for the source and binary and the .gz.asc that will need to be uploaded.
| 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.
For now, the distributions contain Open Office (ODT) formatted guides. However, open them up within Open Office and export them as PDFs: name-of-guide-{roller release version}.pdf. We'll place PDFs in the "docs" folder of the distribution (Step #5).
If you haven't already, you will also need to upload your public key to the KEYS file in the Roller distribution folder. 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, do an empty checkout of the folder (to avoid downloading the several large artifacts in this folder's hierarchy) and then an individual file 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 copy https://svn.apache.org/repos/asf/roller/branches/roller_5.0 https://svn.apache.org/repos/asf/roller/tags/roller_5.0.4-rc1
or
svn copy https://svn.apache.org/repos/asf/roller/trunk https://svn.apache.org/repos/asf/roller/tags/roller_5.1.0-rc1 |
5. Move artifacts to Roller Dist - Dev folder and Vote on release
...
Call for a release vote on the DEV list and once the release is approved, move to the next step. This file's JIRA list of solved Bugs, Improvements, etc. can be obtained from the "Road Map" JIRA tab, selecting the desired version's Release Notes, and then the Configure Release Notes button (choose Text output). If there are any not-yet-publicized security issues that the patch fixes, don't mention them in that public email but do so instead on the separate Roller private (PMC-only) list.
...
Make the announcement on the mailing list and other places, and update the branch to the next snapshot version (e.g., 5.0.4 to 5.0.5-SNAPSHOT). Update the JIRA as explained at the bottom of the Apache CXF release management page.