[jboss-dev-forums] [JBoss Transactions Development] - Narayana Release Process
Tom Jenkinson
do-not-reply at jboss.com
Thu Apr 26 13:56:47 EDT 2012
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
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. Run txbridge demo tests
This process is manual at the moment.
make sure install firefox and running these commands from gui terminal:
1. cd JBOSSTS416_SRC
2. export JBOSS_HOME=`pwd`/jboss-as/build/target/jboss-as-7.1.2.Final-SNAPSHOT/
3. cd XTS/xts-install/demo
4. sed -i "s/JBOSS_HOSTNAME/localhost/g" jboss.properties
5. sed -i "s/JBOSS_PORT/8080/g" jboss.properties
6. sed -i "s/JBOSS_URLSTUB/xtsdemowebservices/g" jboss.properties
7. chmod +x build.sh
8. ./build.sh jboss clean build
9. cd ../../../txbridge/demo
10. ant -Djbossas.home=$JBOSS_HOME clean dist
11. cd ../demo-test
12. mvn clean test
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\([._]\)4\([._]\)Final-SNAPSHOT/4\116\24\3Final/"
2. svn commit -m "Updated to version 4.16.4.Final"
2. Tag the release:
1. 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_4_Final/ -m "4.16.4"
3. Build and deploy the release to nexus staging: 1. ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
4. Bump to next version using similar find to above1. 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\([._]\)4\([._]\)Final/4\116\25\3Final-SNAPSHOT/"
2. svn commit -m "Updated to version 4.16.5.Final-SNAPSHOT"
5. Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as https://github.com/jbosstm/jboss-as1. sed -i "s/4.16.4.Final-SNAPSHOT/4.16.5.Final-SNAPSHOT/g" pom.xml
2. git commit - am "Updated to 4.16.5.Final-SNAPSHOT"
3. git push
h2. Release the artifact through Nexus
1. https://repository.jboss.org/nexus/index.html#welcome https://repository.jboss.org/nexus/index.html#welcome
2. login
3. "Staging Repositories"
4. Click tickbox for your repo
5. Click "Close"
6. Click tickbox again now it is closed
7. Click "Release"
h2. JIRA Release
1. 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
1. https://issues.jboss.org/browse/AS7 https://issues.jboss.org/browse/AS7
2. cd AS source
3. git checkout -b AS7-<JIRANUMBER>
4. sed -i "s/4.16.3.Final/4.16.4.Final/g" pom.xml
5. git commit - am "AS7-<JIRA> Updated to 4.16.4.Final"
6. git push
h2. Update Website
Update the Narayana community site:
* Documentation
* Downloads
* Magnolia (using file generated in build-release-pkgs.xml)
h2. 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 mailto:jbossts-announce at redhat.com jbossts-announce at redhat.com
2. Forum
3. Blog - as appropriate
--------------------------------------------------------------
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&containerType=14&container=2041]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20120426/d1e1eb42/attachment.html
More information about the jboss-dev-forums
mailing list