This page provides a list of instructions that must be done in order when doing a release of Narayana.
Check JIRA
- 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:
- http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java6/
- 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.
- Build narayana
- Build the target JBossAS, aftr updating the narayan dep in the root pom.xml
- Run the unit, interop and crash recovery tests.
Do Release
- Update the version number in any text files:
- 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/"
- 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"
- Build and deploy the release to nexus: ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
- Bump to next version using similar find to above
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'.
You can use the https://github.com/jbosstm/jboss-as project to raise the pull req if you like
Update Website
Update the Narayana community site:
- Documentation
- Downloads
- Magnolia (using file generated in build-release-pkgs.xml)
JIRA Release
- Close all issues in the current release.
- Mark as released.
Promote
Promote the release through the following channels:
- Forum
- Email jbosstm-announce@redhat.com
- Blog