THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
All tags in the subversion repository are meant to be read-only archives of versions of Roller that went final. If you are ever looking for the code to a specific version of Roller you should look here. In roller svn this is at tags/*.
How a release happens
Creating a new release from the trunk
coming soon.
Creating a patch release from an old version
coming soon.
An Example
Let's assume that Roller has just recently released version 2.0 and the code repository is as follows ...
...
| Code Block |
|---|
branches/roller_2.2 (created from trunk after last 2.2 release, represents potential 2.2.1 release)
trunk (now represents 3.0 release, includes Anil's tag work)
branches/roller_4.0 (created for new major release work)
|
Step-by-step How to Create a Release
NOTE: these instructions are for the Roller 5.0 branch and with Roller 5.1 (yet to be released) these instructions will change.
Create release for Tomcat
The commands below will create the Roller for Tomcat release bundle in ZIP and Gzipped TAR formats and the ASCii signature files:
| Code Block |
|---|
./build-tomcat-release.sh ./sign-tomcat-release.sh |
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, files will be in the roller/dist directory.
Upload files for review
Upload to your home directory on people.apache.org, for example for RC1 you might put them here:
| Code Block |
|---|
/home/<username>/public_html/rc1
|
Vote on release
Call for a release vote and once the release is approved, move to the next step.
Move release files into place
Login to people.apache.org and move the release files into the directory tree in the right place. For example, for a Roller 5.0.2 release files would go under the roller-5 directory.
| Code Block |
|---|
/www/www.apache.org/dist/roller/roller-5/v5.0.2/src
/www/www.apache.org/dist/roller/roller-5/v5.0.2/docs
/www/www.apache.org/dist/roller/roller-5/v5.0.2/bin
|
Wait 24 hours for mirrors to update. Once that happens you should delete the old release files for previous versions of Roller. They are already archived elsewhere by the infrastructure team.
Update the website to point to the new files
Update the website files in SVN and update to publish.
Announce the release
Make the announcement on the mailing list and other places.