...
- Check if the release year for Web UI footer is updated (the property
<release-year>
inhadoop-project/pom.xml
). If not, create a JIRA to update the property value to the right year, and propagate the fix from trunk to all necessary branches. Consider the voting time needed before publishing, it's better to use the year of (current time + voting time) here, to be consistent with the publishing time. - In JIRA, ensure that only issues in the "Fixed" state have a "Fix Version" set to release X.Y.Z.
- Verify that $HOME/.gpg defaults to the key listed in the KEYS file.
For the Apache release, a machine capable of running Docker- and Internet- capable, build the release candidate with
create-release
. Unless the--logdir
is given, logs will be in thepatchprocess/
directory. Artifacts will be in the target/artifacts NOTE: This will take quite a while, since it will download and build the entire source tree, including documentation and native components, from scratch to avoid maven repository caching issues hiding issues with the source release.No Format dev-support/bin/create-release --asfrelease --docker --dockercache
While it should fail
create-release
if there are issues, doublecheck the rat log to find and fix any potential licensing issues.No Format grep 'Rat check' patchprocess/mvn_apache_rat.log
- Check that release files look ok - e.g. install it somewhere fresh and run examples from tutorial, do a fresh build, read the release notes looking for WARNINGs, etc.
- Set environment variable version for later steps.
export version=X.Y.Z-RCN
Tag the release candidate:
No Format git tag -s release-$version -m "Release candidate - $version"
- Push branch-X.Y.Z and the newly created tag to the remote repo.
(This is for branch-2.10 only.
mvn deploy
is invoked by the dev-support/bin/create-release script of 3.0.0 and above. see HADOOP-15058.)
Deploy the maven artifacts, on your personal computer. Please be sure you have completed the prerequisite step of preparing thesettings.xml
file before the deployment. You might want to do this in private and clear your history file as your gpg-passphrase is in clear text.No Format mvn deploy -Psign,dist -DskipTests -DskipShade
Copy release files to a public place and ensure they are readable. Note that
home.apache.org
only supports SFTP, so this may be easier with a graphical SFTP client like Nautilus, Konqueror, etc.No Format sftp home.apache.org > cd public_html > mkdir hadoop-${version} > put -r /home/hadoop/hadoop-${version} .... > bye
- Log into Nexus, select "
Staging
Repositories" from the left navigation pane, select the check-box against the specific hadoop repository, andclose
the release. At the time of deploying the maven artifacts, if there are different hadoop items of this release candidate at “Staging Repositories”, drop the stale RC first. - Call a release vote on common-dev at hadoop.apache.org. It's usually a good idea to start the release vote on Monday so that people will have a chance to verify the release candidate during the week. Example
- If the release candidate contains a serious issue, withdraw the vote, make necessary changes, and repeat this process.
- If non-trivial changes are committed to the release branch, ensure the commits are present in the upstream branches.
...