Page History

...

1. Check if the release year for Web UI footer is updated (the property <release-year> in hadoop-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.
2. In JIRA, ensure that only issues in the "Fixed" state have a "Fix Version" set to release X.Y.Z.
3. Verify that $HOME/.gpg defaults to the key listed in the KEYS file.

4. 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 the patchprocess/ 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.

   For x86 architecture CPU, we can use the following command:

   No Format
   dev-support/bin/create-release --asfrelease --docker --dockercache

   Note:

   if we encounter a 401 permission issue, it may be due to the local Maven configuration not being read. We can try the following command.

   Code Block
   dev-support/bin/create-release --asfrelease --docker --dockercache --mvnargs="-Duser.home=<mvn setting.xml path>"

   For Arm architecture CPU, we can use the following command:

   Code Block
   dev-support/bin/create-release --docker --dockercache --mvnargs="-Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false" --deploy --native --sign

   Note:

   
   

   For compiling on ARM architecture CPUsCPU, we can refer to the https://github.com/apache/hadoop-release-support project. 

5. 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

   
   

6. 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.
7. Set environment variable version for later steps. export version=X.Y.Z-RCN

8. Tag the release candidate:

   No Format
   git tag -s release-$version -m "Release candidate - $version"

   
   

9. Push branch-X.Y.Z and the newly created tag to the remote repo.

10. (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 the settings.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

    
    

11. 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

    
    

12. Log into Nexus, select "Staging Repositories" from the left navigation pane, select the check-box against the specific hadoop repository, and close 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.
13. 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
14. If the release candidate contains a serious issue, withdraw the vote, make necessary changes, and repeat this process.
15. If non-trivial changes are committed to the release branch, ensure the commits are present in the upstream branches.

...