QuickFIX/J
Child pages
  • Delivery process

Versions Compared

Old Version 1

changes.mady.by.user Eric Deshayes

Saved on

compared with

New Version Current

changes.mady.by.user Christoph John

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Here is the description of the delivery process.

In order to deliver a new release, the pre-requisite is to have the Bamboo status green.

...

Code Block
eric@odin:~/Projects/quickfixj$ java -version
java version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_22-b03, mixed mode)
eric@odin:~/Projects/quickfixj$ java -versionjava version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_22-b03, mixed mode)

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 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.