Pre Release Check List
- Create an issue in JBQA
- Check that main code base, documentation as well as example code base has been tagged
- Check that Release Notes have been given
- Check that the following builds of Branch 2.7 are successful in Hudson
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-2.7-jdk5/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-2.7-jdk6/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-2.7-selenium-tests/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-2.7-deployment-verification/
- Check that https://svn.jboss.org/repos/portal/tags/TAG_NAME/build/build-thirdparty.xml does not have any dependency on snapshot version of portal modules and other libraries
- For each module in common, test, portlet, web, identity, cms, verify that corresponding tag exists.
- Make sure that dev has given a list of changed modules and for all changed modules, the latest build in hudson has been successful.
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-common-trunk/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-cms-trunk/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-cms-trunk-db/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-identity-trunk/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-portlet-trunk/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-test-trunk/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-web-trunk/
Release Testing Process
- Depending on which module has changed, run corresponding build in hudson after updating the SVN location with tag url and verify that testsuite for the tag is successful.
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-common-release/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-test-release/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-portlet-release/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-cms-release/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-identity-release/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-web-release/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-2.7-db-release/
- http://hudson.qa.jboss.com/hudson/view/JBoss%20Portal/job/jboss-portal-release/
- Pick a machine in QA lab for the rest of the process
$ mkdir release
$ cd release
- release $ svn export https://svn.jboss.org/repos/portal/tags/TAG_NAME project
- release $ svn export https://svn.jboss.org/repos/portal/docs/tags/TAG_NAME docs
- release $ svn export https://svn.jboss.org/repos/portal/examples/tags/TAG_NAME examples
- release $ unzip JBoss AS version that is going to be bundled with (It's usually the latest JBoss AS version in 4 series)
- release $ cd docs
- release/docs $ mvn package
- release/docs $ cd ../project/build
- release/project/build $ sh build.sh
- release/project/build $ export JBOSS_HOME=$PWD/../../jboss-4.2.3.GA
- release/project/build $ ant -f distrib.xml (Ant version 1.7 or higher)
Sanity check:
- Check the filenames in release/project/build/output and verify that name tallies with the version number of the releaswe
- Check in the bundle version that bin/run.conf and bin/run.bat has the -XX:MaxPermSize=256m option
- Start the bundle version, check that the version number in browser title matches.
- Deploy jboss-portal.sar from non bundle version to a fresh install of JBoss AS and verify that you get a clean startup
- Deploy jboss-portal-ha.sar from cluster version to "all" server configuration of a fresh install of JBoss AS and verify that you get a clean startup
- Check that there is an examples directory at the root of the binary and bundle versions. Verify that examples deploy correctly.
Upload to SourceForge
- We need to upload src, binary and MD5 sums.
sftp jbossqa@frs.sourceforge.net. If you don't know the password, ask your teammate. If you don't know who to ask, this wiki is not for you.
- Once bits have been uploaded, download bundle version and verify that server starts without problem. This verifies that bits did not get corrupted during upload.
- Send a note to JBoss Portal ML with Sourceforge download URL.
- Update Jira issue with Sourceforge download URL
Comments