Tom Jenkinson [
https://community.jboss.org/people/tomjenkinson] modified the document:
"Narayana Release Process"
To view the document, visit:
https://community.jboss.org/docs/DOC-17433
--------------------------------------------------------------
This page provides a list of instructions that must be done *in order* when doing a
release of Narayana.
h2. Check JIRA
1. Ensure all issues are resolved. Any outstanding issues must be pushed back or
resolved.
h2. Check Hudson
Ensure no test failures in the following group of hudson tests:
1.
http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java6/
http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java6/
2.
http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java7/
http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java7/
h2. DEPRECATED BY JBTM-1063
h2. Run XTS Tests
This process is manual at the moment. Paul needs to do this.
0.1. Build narayana
0.2. Build the target JBossAS, aftr updating the narayan dep in the root pom.xml
0.3. Run the unit, interop and crash recovery tests.
h2. 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/branches/JBOSSTS_4_16
https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_3_Final/
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 https://github.com/jbosstm/jboss-as
h2. Update Website
Update the Narayana community site:
* Documentation
* Downloads
* Magnolia (using file generated in build-release-pkgs.xml)
h2. JIRA Release
1. Close all issues in the current release.
2. Mark as released.
h2. 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
h2. Promote
Promote the release through the following channels:
1. Forum
2. Email mailto:jbosstm-announce@redhat.com jbosstm-announce(a)redhat.com
3. Blog
--------------------------------------------------------------
Comment by going to Community
[
https://community.jboss.org/docs/DOC-17433]
Create a new document in JBoss Transactions Development at Community
[
https://community.jboss.org/choose-container!input.jspa?contentType=102&a...]