Follow these steps for an official release.
- You need to have access to http://ci.hibernate.org/: the release process is now driven by CI
- Update the TCK audit file (tests/src/main/resources/tck-audit.xml) as per the latest spec revision and check that it was identical to the preexisting file. If not, you will probably need to update the TCK assertion ids accordingly.
- Check that everything has been pushed to the upstream repository
- Check that CI is green
- Check that the BV and HV versions referenced in the parent pom.xml are alright (non SNAPSHOT and pointing to the right release)
- Before you release, deploy the TCK and run the Validator tests with this version of the TCK to check everything is OK (run the TCK in container mode)
- Make sure there are no outstanding issues in Jira
- Release the Jira version
- Do NOT update the changelog.txt and README.md, the release job does it for you.
- Go to CI, and select the beanvalidation-tck-release job. Click on Build with parameters.
- Be careful when filling the form with the build parameters.
- Release the artifacts on the JBoss Nexus repository manager. This is a two-steps process.
- Log into Nexus and examine your staging repository. Click on the Updated column 2 times to have the repositories sorted correctly.
- You can either drop it in order to start over again or you can close and promote it making the artifacts available in the live repository. (Click Refresh after each action)
- You can find more information in the description of the JBoss project release process. A Maven settings.xml for testing the artifacts in the staging repository can be found here.
- Transfer the released issues in JIRA to the Closed state. You can use this search Issue Navigator - Hibernate JIRA and select another fixVersion. Once you have selected the right version, click on the button with three dots at the top right of the screen and click on Bulk update all XX issues. Use the Transition action to transition your issues from Resolved to Closed.
NOTE: In the HTML version of the reference guide, some special characters and the section titles will show up not correctly when opening the file locally. This is a known issue, the documentation looks correct when retrieved via Apache.
- The CI job automatically pushes the distribution to SourceForge and publishes the documentation to docs.jboss.org.