In order to deliver a new release, the pre-requisite is to have the Bamboo status green.
Another pre-requisite is to have a JDK5 and a JDK 1.4 as these java versions are still supported.
Make sure that the version of java is 1.5 when the packaging is done by doing a java -version.
If the Bamboo status is green, the packaging can be launched.
At the same time, the trunk can be tagged using the usual tag name QFJ_RELEASE_x_y_z.
The packaging is done using the Ant build.xml script that is available under quickfixj. You might have to update the jvm.java4 property to match your jdk 1.4 location:
The target to launch is release.versioned. The release version will have to be entered:
After a few minutes, you will find the binaries under the dist directory:
You can then log in into the quickfixj source forge file and go to the Files section (http://sourceforge.net/projects/quickfixj/files/QuickFIX_J/).
Then add a new folder with the version name and select the staging option in order to have the files hidden until the delivery process is completed.
All the *.zip and *.tar.gz files can be uploaded.
Then, a release note has to be published.
The release note has to be published as a sourceforge news (that you can find under Developer->News and then submit) and sent to the QFJ developers and QFJ users mailing lists.
Note that the SourceForge news will be updated automatically to the Quickfix/J web site.
A release note draft can be generated from JIRA will all the JIRA associated to the version set in JIRA and against which issues have be set as fixed. Afterwards the JIRA version needs to be closed.
Then, once you are happy will your release note, you need to modify the staging flag of the directory where the files have been uploaded and send the release note email and the sourceforge news.
Additionally, the links on http://www.quickfixj.org/documentation/ have to be changed to point to the new version.