[JBoss Transactions Development] - Narayana Release Process
by Tom Jenkinson
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 (for the branch you intend to release):
* 4.16 Branch : jbossts-branch416-*
* 4.17 Branch : jbossts-branch417-*
* 5 Branch: jbossts-narayana-*
h2. Do Release
h5.
h5. svn branches
#Make sure your checkout has no local changes
svn update
svn status
POINT_VERSION=5
NEXT_POINT_VERSION=6
#Update the version in 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\([._]\)${POINT_VERSION}\([._]\)Final-SNAPSHOT/4\116\2$POINT_VERSION\3Final/"
svn commit -m "Updated to version 4.16.$POINT_VERSION.Final"
#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_${POINT_V... -m "4.16.$POINT_VERSION"
#Build and deploy the release to nexus staging:
ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
#Bump to next version using similar find to above
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\([._]\)${POINT_VERSION}\([._]\)Final/4\116\2${NEXT_POINT_VERSION}\3Final-SNAPSHOT/"
svn commit -m "Updated to version 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT"
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
sed -i "s/4.16.${POINT_VERSION}.Final-SNAPSHOT/4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT/g" pom.xml
git commit - am "Updated to 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT"
git push
h5.
h5. git branches
#Make sure your checkout has no local changes
git checkout master
git status
#Pull remote changes
git fetch
git reset --hard upstream/master
#Update the version in text files and tag and push the release
CHANGE:
current='4\([._]\)17\([._]\)0\([._]\)Final-SNAPSHOT'
next='4\117\20\3Final'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git commit -am "Updated to $next"
git tag 4.17.0.Final
git push upstream master
git push upstream --tags
#Bump to next version using similar find to above
CHANGE:
current='4\([._]\)17\([._]\)0\([._]\)Final'
next='5\10\20\3M2-SNAPSHOT'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git push upstream master
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
git clone -o jbosstm https://github.com/jbosstm/jboss-as
git checkout 5_BRANCH
sed -i "s/5.0.0.M1-SNAPSHOT/5.0.0.M2-SNAPSHOT/g" pom.xml
git commit -am "Updated to 5.0.0.M2-SNAPSHOT"
git push jbosstm 5_BRANCH
#Build and deploy the release to nexus staging:
CHANGE:
ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
h2. Release Quickstarts and Docs
current='4\([._]\)17\([._]\)0\([._]\)Final-SNAPSHOT'
next='4\117\20\3Final'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git commit -am "Updated to $next"
git tag 4.17.0.Final
current='4\([._]\)17\([._]\)0\([._]\)Final'
next='5\10\20\3M2-SNAPSHOT'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git push upstream master --tags
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. Dont worry about a description, just click "Close"
7. Click tickbox after it is closed
8. Click "Release"
9. Again a description doesn't matter
h2. Upload the distribution jbosstm(a)filemgmt.jboss.org < WORK IN PROGRESS > (Not for point releases)
1. export VERSION=5.0.0.M2
2. mkdir ~/filemgmt.jboss.org/
3. sshfs mailto:jbosstm@filemgmt.jboss.org jbosstm(a)filemgmt.jboss.org: ~/filemgmt.jboss.org/
4. mkdir -p ~/filemgmt.jboss.org/downloads_htdocs/jbosstm/$VERSION/binary
5. mkdir -p ~/filemgmt.jboss.org/downloads_htdocs/jbosstm/$VERSION/src
6. mkdir -p ~/filemgmt.jboss.org/docs_htdocs/jbosstm/$VERSION/api/
7. mkdir -p ~/filemgmt.jboss.org/docs_htdocs/jbosstm/$VERSION/guides/
8. Upload the build files to those folders
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
7. Raise a pull request
h2. Update Website
Update the Narayana community site:
* Documentation
* Downloads
* Magnolia (using file generated in build-release-pkgs.xml), also update the front page announcement and the release notes link
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 jbossts-announce(a)lists.jboss.org (mailto:jbossts-announce@lists.jboss.org)
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&c...]
12 years, 3 months
[JBoss Transactions Development] - Narayana Release Process
by Tom Jenkinson
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 (for the branch you intend to release):
* 4.16 Branch : jbossts-branch416-*
* 4.17 Branch : jbossts-branch416-*
* 5 Branch: ?
h2. Do Release
h5. 4.16 Branch
#Make sure your checkout has no local changes
svn update
svn status
POINT_VERSION=5
NEXT_POINT_VERSION=6
#Update the version in 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\([._]\)${POINT_VERSION}\([._]\)Final-SNAPSHOT/4\116\2$POINT_VERSION\3Final/"
svn commit -m "Updated to version 4.16.$POINT_VERSION.Final"
#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_${POINT_V... -m "4.16.$POINT_VERSION"
#Build and deploy the release to nexus staging:
ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
#Bump to next version using similar find to above
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\([._]\)${POINT_VERSION}\([._]\)Final/4\116\2${NEXT_POINT_VERSION}\3Final-SNAPSHOT/"
svn commit -m "Updated to version 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT"
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
sed -i "s/4.16.${POINT_VERSION}.Final-SNAPSHOT/4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT/g" pom.xml
git commit - am "Updated to 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT"
git push
h5. 5 Branch
#Make sure your checkout has no local changes
git checkout master
git status
#Pull remote changes
git fetch
git reset --hard upstream/master
#Update the version in text files and tag and push the release
CHANGE:
current='4\([._]\)17\([._]\)0\([._]\)Final-SNAPSHOT'
next='4\117\20\3Final'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git commit -am "Updated to $next"
git tag 4.17.0.Final
git push upstream master
git push upstream --tags
#Build and deploy the release to nexus staging:
CHANGE:
ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
#Bump to next version using similar find to above
CHANGE:
current='4\([._]\)17\([._]\)0\([._]\)Final'
next='5\10\20\3M2-SNAPSHOT'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git push upstream master
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
git clone -o jbosstm https://github.com/jbosstm/jboss-as
git checkout 5_BRANCH
sed -i "s/5.0.0.M1-SNAPSHOT/5.0.0.M2-SNAPSHOT/g" pom.xml
git commit -am "Updated to 5.0.0.M2-SNAPSHOT"
git push jbosstm 5_BRANCH
h2. Release Quickstarts and Docs
current='4\([._]\)17\([._]\)0\([._]\)Final-SNAPSHOT'
next='4\117\20\3Final'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git commit -am "Updated to $next"
git tag 4.17.0.Final
current='4\([._]\)17\([._]\)0\([._]\)Final'
next='5\10\20\3M2-SNAPSHOT'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git push upstream master --tags
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. Dont worry about a description, just click "Close"
7. Click tickbox after it is closed
8. Click "Release"
9. Again a description doesn't matter
h2. Upload the distribution jbosstm(a)filemgmt.jboss.org < WORK IN PROGRESS > (Not for point releases)
1. export VERSION=5.0.0.M2
2. mkdir ~/filemgmt.jboss.org/
3. sshfs mailto:jbosstm@filemgmt.jboss.org jbosstm(a)filemgmt.jboss.org: ~/filemgmt.jboss.org/
4. mkdir -p ~/filemgmt.jboss.org/downloads_htdocs/jbosstm/$VERSION/binary
5. mkdir -p ~/filemgmt.jboss.org/downloads_htdocs/jbosstm/$VERSION/src
6. mkdir -p ~/filemgmt.jboss.org/docs_htdocs/jbosstm/$VERSION/api/
7. mkdir -p ~/filemgmt.jboss.org/docs_htdocs/jbosstm/$VERSION/guides/
8. Upload the build files to those folders
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
7. Raise a pull request
h2. Update Website
Update the Narayana community site:
* Documentation
* Downloads
* Magnolia (using file generated in build-release-pkgs.xml), also update the front page announcement and the release notes link
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 jbossts-announce(a)lists.jboss.org (mailto:jbossts-announce@lists.jboss.org)
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&c...]
12 years, 3 months
[JBoss Transactions Development] - Narayana Release Process
by Tom Jenkinson
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 (for the branch you intend to release):
* 4.16 Branch : jbossts-branch416-*
* 4.17 Branch : jbossts-branch416-*
* 5 Branch: ?
h2. Do Release
h5. 4.16 Branch
#Make sure your checkout has no local changes
svn update
svn status
POINT_VERSION=5
NEXT_POINT_VERSION=6
#Update the version in 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\([._]\)${POINT_VERSION}\([._]\)Final-SNAPSHOT/4\116\2$POINT_VERSION\3Final/"
svn commit -m "Updated to version 4.16.$POINT_VERSION.Final"
#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_${POINT_V... -m "4.16.$POINT_VERSION"
#Build and deploy the release to nexus staging:
ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
#Bump to next version using similar find to above
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\([._]\)${POINT_VERSION}\([._]\)Final/4\116\2${NEXT_POINT_VERSION}\3Final-SNAPSHOT/"
svn commit -m "Updated to version 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT"
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
sed -i "s/4.16.${POINT_VERSION}.Final-SNAPSHOT/4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT/g" pom.xml
git commit - am "Updated to 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT"
git push
h5. 5 Branch
#Make sure your checkout has no local changes
git checkout master
git status
#Pull remote changes
git fetch
git reset --hard upstream/master
#Update the version in text files and tag and push the release
CHANGE:
current='4\([._]\)17\([._]\)0\([._]\)Final-SNAPSHOT'
next='4\117\20\3Final'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git commit -am "Updated to $next"
git tag 4.17.0.Final
git push upstream master
git push upstream --tags
#Build and deploy the release to nexus staging:
CHANGE:
ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
#Bump to next version using similar find to above
CHANGE:
current='4\([._]\)17\([._]\)0\([._]\)Final'
next='5\10\20\3M2-SNAPSHOT'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git push upstream master
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
git clone -o jbosstm https://github.com/jbosstm/jboss-as
git checkout 5_BRANCH
sed -i "s/5.0.0.M1-SNAPSHOT/5.0.0.M2-SNAPSHOT/g" pom.xml
git commit -am "Updated to 5.0.0.M2-SNAPSHOT"
git push jbosstm 5_BRANCH
h2. Release Quickstarts and Docs
Todo
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. Dont worry about a description, just click "Close"
7. Click tickbox after it is closed
8. Click "Release"
9. Again a description doesn't matter
h2. Upload the distribution jbosstm(a)filemgmt.jboss.org < WORK IN PROGRESS > (Not for point releases)
1. export VERSION=5.0.0.M2
2. mkdir ~/filemgmt.jboss.org/
3. sshfs mailto:jbosstm@filemgmt.jboss.org jbosstm(a)filemgmt.jboss.org: ~/filemgmt.jboss.org/
4. mkdir -p ~/filemgmt.jboss.org/downloads_htdocs/jbosstm/$VERSION/binary
5. mkdir -p ~/filemgmt.jboss.org/downloads_htdocs/jbosstm/$VERSION/src
6. mkdir -p ~/filemgmt.jboss.org/docs_htdocs/jbosstm/$VERSION/api/
7. mkdir -p ~/filemgmt.jboss.org/docs_htdocs/jbosstm/$VERSION/guides/
8. Upload the build files to those folders
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
7. Raise a pull request
h2. Update Website
Update the Narayana community site:
* Documentation
* Downloads
* Magnolia (using file generated in build-release-pkgs.xml), also update the front page announcement and the release notes link
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 jbossts-announce(a)lists.jboss.org (mailto:jbossts-announce@lists.jboss.org)
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&c...]
12 years, 3 months
[JBoss Transactions Development] - Narayana Release Process
by Tom Jenkinson
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 (for the branch you intend to release):
* 4.16 Branch : jbossts-branch416-*
* 4.17 Branch : jbossts-branch416-*
* 5 Branch: ?
h2. Do Release
h5. 4.16 Branch
#Make sure your checkout has no local changes
svn update
svn status
POINT_VERSION=5
NEXT_POINT_VERSION=6
#Update the version in 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\([._]\)${POINT_VERSION}\([._]\)Final-SNAPSHOT/4\116\2$POINT_VERSION\3Final/"
svn commit -m "Updated to version 4.16.$POINT_VERSION.Final"
#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_${POINT_V... -m "4.16.$POINT_VERSION"
#Build and deploy the release to nexus staging:
ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
#Bump to next version using similar find to above
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\([._]\)${POINT_VERSION}\([._]\)Final/4\116\2${NEXT_POINT_VERSION}\3Final-SNAPSHOT/"
svn commit -m "Updated to version 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT"
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
sed -i "s/4.16.${POINT_VERSION}.Final-SNAPSHOT/4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT/g" pom.xml
git commit - am "Updated to 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT"
git push
h5. 5 Branch
#Make sure your checkout has no local changes
git checkout master
git status
#Pull remote changes
git fetch
git reset --hard upstream/master
#Update the version in text files and tag and push the release
CHANGE:
current='4\([._]\)17\([._]\)0\([._]\)Final-SNAPSHOT'
next='4\117\20\3Final'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git commit -am "Updated to $next"
git tag 4.17.0.Final
git push upstream master
git push upstream --tags
#Build and deploy the release to nexus staging:
CHANGE:
ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
#Bump to next version using similar find to above
CHANGE:
current='4\([._]\)17\([._]\)0\([._]\)Final'
next='5\10\20\3M2-SNAPSHOT'
find . -name \*.java -o -name \*.xml -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | xargs sed -i "s/"$current"/"$next"/"
git push upstream master
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
CHANGE:
git checkout 5_BRANCH
sed -i "s/5.0.0.M1-SNAPSHOT/5.0.0.M2-SNAPSHOT/g" pom.xml
git commit - am "Updated to 5.0.0.M2-SNAPSHOT"
git push
h2. Release Quickstarts and Docs
Todo
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. Dont worry about a description, just click "Close"
7. Click tickbox after it is closed
8. Click "Release"
9. Again a description doesn't matter
h2. Upload the distribution jbosstm(a)filemgmt.jboss.org < WORK IN PROGRESS > (Not for point releases)
1. export VERSION=5.0.0.M2
2. mkdir ~/filemgmt.jboss.org/
3. sshfs mailto:jbosstm@filemgmt.jboss.org jbosstm(a)filemgmt.jboss.org: ~/filemgmt.jboss.org/
4. mkdir -p ~/filemgmt.jboss.org/downloads_htdocs/jbosstm/$VERSION/binary
5. mkdir -p ~/filemgmt.jboss.org/downloads_htdocs/jbosstm/$VERSION/src
6. mkdir -p ~/filemgmt.jboss.org/docs_htdocs/jbosstm/$VERSION/api/
7. mkdir -p ~/filemgmt.jboss.org/docs_htdocs/jbosstm/$VERSION/guides/
8. Upload the build files to those folders
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
7. Raise a pull request
h2. Update Website
Update the Narayana community site:
* Documentation
* Downloads
* Magnolia (using file generated in build-release-pkgs.xml), also update the front page announcement and the release notes link
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 jbossts-announce(a)lists.jboss.org (mailto:jbossts-announce@lists.jboss.org)
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&c...]
12 years, 3 months
[JBoss AS 7 Development] - Jboss7 dependencies pratique : how to manage the version part of the a lib like {artifactId}-{version}.jar?
by yunshi tan
yunshi tan [https://community.jboss.org/people/yunshi] created the discussion
"Jboss7 dependencies pratique : how to manage the version part of the a lib like {artifactId}-{version}.jar?"
To view the discussion, visit: https://community.jboss.org/message/761317#761317
--------------------------------------------------------------
Hi everyone,
In Jboss7, we need to point out explicit dependencies, in META-INFO/MANIFEST.MF or in jboss-deployment-structure.xml.
My problem is, my applications are named as *{artifactId}-{version}.jar.*
As a result, in the jboss-deployment-structure.xml, I have to include the *{version}* part in the independency declaration. That's to say, each time I release a project who is depended by another projects, I have to update the {version} part manually in the jboss-deployment-structure.xml of those projects.I find it not very funny. :(
Another thing very annoying, I have some EJB jars having the version in their name, like *ejb-1.0-SNAPSHOT.jar*. Therefore, to search the ejb from JNDI, i have to call search the name as : "java:global/*ejb-1.0-SNAPSHOT*/someDAOImpl!com.xxx.dao.web.local.someDAOLocal". That means after each release, hte JNDI name changes ! :( :( :(
Does any body have some pratcical advices or experience pls ? That would be very nice. Many thx in advance.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/761317#761317]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 3 months
[JBoss Transactions Development] - Narayana Release Process
by Paul Robinson
Paul Robinson [https://community.jboss.org/people/paul.robinson] 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 (for the branch you intend to release):
* 4.16 Branch : jbossts-branch416-*
* 4.17 Branch : jbossts-branch416-*
* 5 Branch: ?
h2. Do Release
h5. 4.16 Branch
#Make sure your checkout has no local changes
svn update
svn status
#Update the version in 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\([._]\)4\([._]\)Final-SNAPSHOT/4\116\24\3Final/"
svn commit -m "Updated to version 4.16.4.Final"
#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_4_Final/ -m "4.16.4"
#Build and deploy the release to nexus staging:
ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
#Bump to next version using similar find to above
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/"
svn commit -m "Updated to version 4.16.5.Final-SNAPSHOT"
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
sed -i "s/4.16.4.Final-SNAPSHOT/4.16.5.Final-SNAPSHOT/g" pom.xml
git commit - am "Updated to 4.16.5.Final-SNAPSHOT"
git push
h5. 5 Branch
#Make sure your checkout has no local changes
git checkout master
git status
#Pull remote changes
git fetch
git rebase -i master
#Update the version in text files
CHANGE:
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/"
svn commit -m "Updated to version 4.16.4.Final"
#Tag the release:
TODO
#Build and deploy the release to nexus staging:
CHANGE:
ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia
#Bump to next version using similar find to above
CHANGE:
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/"
svn commit -m "Updated to version 4.16.5.Final-SNAPSHOT"
#Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as
CHANGE:
sed -i "s/4.16.4.Final-SNAPSHOT/4.16.5.Final-SNAPSHOT/g" pom.xml
git commit - am "Updated to 4.16.5.Final-SNAPSHOT"
git push
h2. Release Quickstarts and Docs
Todo
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. Dont worry about a description, just click "Close"
7. Click tickbox after it is closed
8. Click "Release"
9. Again a description doesn't matter
h2. Upload the distribution jbosstm(a)filemgmt.jboss.org < WORK IN PROGRESS >
1. export VERSION=5.0.0.M2
2. mkdir ~/filemgmt.jboss.org/
3. sshfs mailto:jbosstm@filemgmt.jboss.org jbosstm(a)filemgmt.jboss.org: ~/filemgmt.jboss.org/
4. mkdir -p ~/filemgmt.jboss.org/downloads_htdocs/jbosstm/$VERSION/binary
5. mkdir -p ~/filemgmt.jboss.org/downloads_htdocs/jbosstm/$VERSION/src
6. mkdir -p ~/filemgmt.jboss.org/docs_htdocs/jbosstm/$VERSION/api/
7. mkdir -p ~/filemgmt.jboss.org/docs_htdocs/jbosstm/$VERSION/guides/
8. Upload the build files to those folders
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
7. Raise a pull request
h2. Update Website
Update the Narayana community site:
* Documentation
* Downloads
* Magnolia (using file generated in build-release-pkgs.xml), also update the front page announcement and the release notes link
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 jbossts-announce(a)lists.jboss.org (mailto:jbossts-announce@lists.jboss.org)
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&c...]
12 years, 3 months