Things to do before issuing a new release:
Ensure all new Configuration parameters are documented
Use your IDE to regenerate equals/hashCode for ConfigurationImpl (this is just much safer than trying to inspect the code).
Ensure all public API classes have a proper Javadoc.
Update docs/user-manual/en/versions.md to include appropriate release notes and upgrade instructions. See previous entries for guidance.
Bump the version numbers in example and test poms to the next release version. e.g. 2.0.0
Build the release locally: mvn clean install -Prelease
Test the standalone release (this should be done on windows as well as linux):
If everything is successful follow these next steps to build and publish artifacts to Nexus and send out a release vote.
If you don't have a key to sign the release artifacts, follow the instruction at apache release signing.
Ensure that your key is listed at https://dist.apache.org/repos/dist/release/activemq/KEYS. If not, generate the key information, e.g.:
gpg --list-sigs username@apache.org > /tmp/key; gpg --armor --export username@apache.org >> /tmp/key
Then send the key information in /tmp/key to private@activemq.apache.org so it can be added.
Ensure that your key is listed at https://home.apache.org/keys/committer/. If not add your key id (available via gpg --fingerprint <key>) to the OpenPGP Public Key Primary Fingerprint field at https://id.apache.org/. Note: this is just the key id, not the whole fingerprint.
Before starting make sure you clone a brand new git as follows as the release plugin will use the upstream for pushing the tags:
git clone git://github.com/apache/activemq-artemis.git cd activemq-artemis git remote add upstream https://gitbox.apache.org/repos/asf/activemq-artemis.git
If your git user.email and/or user.name are not set globally then you'll need to set these on the newly clone repository as they will be used during the release process to make commits to the upstream repository, e.g.:
git config user.email "username@apache.org" git config user.name "FirstName LastName"
This should be the same user.email and user.name you use on your main repository.
You will have to use this following maven command to perform the release:
mvn clean release:prepare -DautoVersionSubmodules=true -Prelease
You could optionally set pushChanges=false so the version commit and tag won't be pushed upstream (you would have to do it yourself):
mvn clean release:prepare -DautoVersionSubmodules=true -DpushChanges=false -Prelease
When prompted make sure the next is a major release. Example:
[INFO] Checking dependencies and plugins for snapshots ... What is the release version for "ActiveMQ Artemis Parent"? (org.apache.activemq:artemis-pom) 2.19.0: : What is SCM release tag or label for "ActiveMQ Artemis Parent"? (org.apache.activemq:artemis-pom) artemis-pom-2.19.0: : 2.19.0 What is the new development version for "ActiveMQ Artemis Parent"? (org.apache.activemq:artemis-pom) 2.19.1-SNAPSHOT: : 2.20.0-SNAPSHOT
Otherwise snapshots will be created at 2.19.1-SNAPSHOT and forgotten. (Unless we ever release 2.19.1 on that example).
For more information look at the prepare plugin:
If you set pushChanges=false then you will have to push the changes manually. The first command is to push the commits which are for changing the <version> in the pom.xml files, and the second push is for the tag, e.g.:
git push upstream git push upstream <version>
Ensure that your environment is ready to deploy to the ASF Nexus repository as described at Publishing Maven Artifacts
Copy the file release.properties, that is generated at the root of the project during the release, before starting the upload. You could need it if the upload fails.
To upload it to nexus, perform this command:
mvn release:perform -Prelease
Note: this can take quite a while depending on the speed for your Internet connection. If the upload fails or is interrupted, remove the incomplete repository using the “Drop” button on Nexus website. Before starting the upload again, check the release.properties at the root of the project.
If something happened during the release upload to nexus, you may need to eventually redo the upload. Remove the incomplete repository using the “Drop” button on Nexus website. Before starting the upload again, check the release.properties at the root of the project.
There is a release.properties file that is generated at the root of the project during the release. In case you want to upload a previously tagged release, add this file as follows:
scm.url=scm:git:https://github.com/apache/activemq-artemis.git scm.tag=1.4.0
Give the staging repository contents a quick inspection using the content navigation area, then proceed to close the staging repo using the “Close” button on Nexus website, locking it from further modification and exposing its contents at a staging URL to allow testing. Set a description such as “ActiveMQ Artemis (RC1)” while closing.
Use the closed staging repo contents to populate the dist dev svn area with the official release artifacts for voting. Use the script already present in the repo to download the files and populate a new ${CURRENT-RELEASE} dir:
svn co https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/ cd activemq-artemis ./prepare-release.sh https://repository.apache.org/content/repositories/orgapacheactivemq-${NEXUS-REPO-ID} ${CURRENT-RELEASE}
Give the files a check over and commit the new dir and start a vote if all looks well.
svn add <version> svn commit
Old staged releases can be cleaned out periodically.
Please, include the git-commit-report as part of the release process. To generate it, follow these steps:
$ git clone https://github.com/rh-messaging/jira-git-report.git $ cd jira-git-report $ mvn compile assembly:single $ cd target $ java -jar jira-git-0.1.SNAPSHOT-jar-with-dependencies.jar artemis <checkoutDirectory>/activemq-artemis <checkoutDirectory>/artemis-website commit-report-<version>.html <previous-version> <version> true
real example used on 2.6.1:
$ java -jar java -jar jira-git-0.1.SNAPSHOT-jar-with-dependencies.jar artemis release-work/activemq-artemis release-work/activemq-website/src/components/artemis/download/commit-report-2.16.0.html 2.15.0 2.16.0 true
Use the git-report to do some JIRA cleanup making sure your commits and JIRA are accurate:
JIRAS on this Report at the bottom of the report.Manage Versions button at the ActiveMQ Artemis Releases pageFix Version field.Once all the artifacts are stage then send an email to dev@activemq.apache.org. It should have a subject like [VOTE] Apache ActiveMQ Artemis <version>. Here is an example for the body of the message:
I would like to propose an Apache ActiveMQ Artemis <version> release. We added these new features as part of <version>: [ARTEMIS-123] - Great new feature 1 [ARTEMIS-456] - Great new feature 2 The release notes can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=<releaseNotesVersionID>&projectId=12315920 Ths git commit report is here: https://activemq.apache.org/components/artemis/download/commit-report-<version> Source and binary distributions can be found here: https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/<version>/ The Maven repository is here: https://repository.apache.org/content/repositories/orgapacheactivemq-<repoID> In case you want to give it a try with the maven repo on examples: https://activemq.apache.org/components/artemis/documentation/hacking-guide/validating-releases.html The source tag: https://gitbox.apache.org/repos/asf/activemq-artemis.git;a=tag;h=refs/tags/<version> I will update the website after the vote has passed. [ ] +1 approve this release [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1
Rules for the Apache voting process are stipulated here.
Assuming the vote is successful send a email with a subject like [RESULT] [VOTE] Apache ActiveMQ Artemis <version> informing the list about the voting results, e.g.:
Results of the Apache ActiveMQ Artemis <version> release vote. Vote passes with 4 votes, 3 binding and 1 non-binding. The following votes were received: Binding: +1 John Doe +1 Jane Doe +1 Bill Smith Non Binding: +1 Mike Williams Thank you to everyone who contributed and took the time to review the release candidates and vote. I'll update the website as soon as the mirrors are updated (I will wait 24 hours after I update SVN). Regards
After a successful vote, populate the dist release area using the staged files from the dist dev area to allow them to mirror. Note: this can only be done by a PMC member.
Use the script already present in the repo to copy the staged files from the dist dev area to the dist release area:
svn co https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/ cd activemq-artemis ./promote-release.sh ${CURRENT-RELEASE}
Good mirror coverage can take up to 24 hours. Mirror status can be viewed here.
Go to https://repository.apache.org/#stagingRepositories and click the “Release” button.
Wait 24 hours after updating SVN to get a good mirror coverage, before proceeding. Mirror status can be viewed here.
Clone the website repository from:
git clone https://gitbox.apache.org/repos/asf/activemq-website.git
Once the mirrors are up-to-date then update the following:
src/components/artemis/download/release-notes-<old-version>.md to src/components/artemis/download/release-notes-<new-version>.md and update it deleting the existing list of bugs, features, improvements, etc. and replacing it with the HTML from the bottom of the release notes url you sent out with your VOTE email (appending &styleName=Text).src/_artemis_releases/artemis-<old-version>-release.md to src/_artemis_releases/artemis-<new-version>-release.md. Update the versions and dates.src/_data/current_releases.yml file if needed.src/components/artemis/documentation/latest to src/components/artemis/documentation/<old-version>.src/components/artemis/documentation/latest and copy these files into it:apache-artemis-<new-version>/web/user-manualgitbook pdf)gitbook epub)gitbook mobi)src/components/artemis/documentation/hacking-guide and copy these files into it:apache-artemis-<new-version>/web/hacking-guidegitbook pdf)src/components/artemis/documentation/javadocs/javadoc-latest to src/components/artemis/documentation/javadocs/javadoc-<old-version>.src/components/artemis/documentation/javadocs/javadoc-latest and copy the contents of apache-artemis-<new-version>/web/api into it.Run git add for all the added directories & files and then git commit -m "updates for <version> release". Once pushed, the changes should be published automatically by the jekyll_websites builder of the apache buildbot.
Note: Generating PDFs, etc. with gitbook requires the installation of Calibre. You can install this manually, but it is recommended you use your platform's package management to install (e.g. sudo apt-get install calibre).
Once the website is updated then send an email with a subject like [ANNOUNCE] ActiveMQ Artemis <version> Released to user@activemq.apache.org & dev@activemq.apache.org, e.g.:
I'm pleased to announce the release of ActiveMQ Artemis <version>. Downloads are now available at: https://activemq.apache.org/components/artemis/download/ For a complete list of updates: https://activemq.apache.org/components/artemis/download/release-notes-<version> I would like to highlight these improvements: - Summary of feature 1: <link to relevant documentation> - Summary of feature 2: <link to relevant documentation> - Summary of feature 3: <link to relevant documentation> As usual it contains a handful of bug fixes and other improvements. Many thanks for all the contributors to this release.
Only the current releases should be mirrored. Older releases must be cleared:
svn rm -m "clean out older release" https://dist.apache.org/repos/dist/release/activemq/activemq-artemis/${OLD-RELEASE}
Any links to them on the site must be updated to reference the ASF archive instead at https://archive.apache.org/dist/activemq/activemq-artemis/ (this should already have been done implicitly in the previous step).
Ensure old releases are only removed after the site is updated in order to avoid broken links.
For more information consult the apache guide at this address: