JBoss Community

Narayana Release Process

modified by Tom Jenkinson in JBoss Transactions Development - View the full document

This page provides a list of instructions that must be done in order when doing a release of Narayana.

 

Check JIRA

  1. Ensure all issues are resolved. Any outstanding issues must be pushed back or resolved.

Check Hudson

Ensure no test failures in the following group of hudson tests:

 

  1. http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java6/
  2. http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java7/

 

DEPRECATED BY JBTM-1063

Run XTS Tests

This process is manual at the moment. Paul needs to do this.

    1. Build narayana
    2. Build the target JBossAS, aftr updating the narayan dep in the root pom.xml
    3. Run the unit, interop and crash recovery tests.

Do Release

  1. Update the version number in any text files:
    1. find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep  -l "4[._]16" | xargs sed -i "s/4\([._]\)16\([._]\)3\([._]\)Final/4\116\24\3Final-SNAPSHOT/"
  2. Tag the release: svn cp https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_3_Final/ -m "4.16.3"
  3. Build and deploy the release to nexus: ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
  4. Bump to next version using similar find to above
  5. Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as

 

Update Website

Update the Narayana community site:

  • Documentation
  • Downloads
  • Magnolia (using file generated in build-release-pkgs.xml)

 

JIRA Release

  1. Close all issues in the current release.
  2. Mark as released.

 

Push Upstream

If appropriate for this release, create a new 'component update' issue in AS7 JIRA. Ensure the module is set to 'transactions' and select an appropriate 'fix for'.

Assign it to yourself

Resolve the work and raise the pull request

 

Promote

NOTE: It is worth waiting for the merge of the pull request before advertising, or at least wait for the merge build notification first ;)

Promote the release through the following channels:

  1. Email jbossts-announce@redhat.com
  2. Forum
  3. Blog - as appropriate

Comment by going to Community

Create a new document in JBoss Transactions Development at Community