Dear Wiki user, You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The "HowToRelease" page has been changed by VinodKumarVavilapalli: https://wiki.apache.org/hadoop/HowToRelease?action=diff&rev1=87&rev2=88 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. 1. In JIRA, ensure that only issues in the "Fixed" state have a "Fix Version" set to release X.Y.Z. - 1. In JIRA, "release" the version, setting the date to the expected end-of-vote date. Visit the "Administer Project" page, then the "Manage versions" page. You need to have the "Admin" role in HADOOP, HDFS, MAPREDUCE, and YARN. This ensures that the release notes and changes file have the correct date to match the actual release date. 1. Verify that $HOME/.gpg defaults to the key listed in the KEYS file. 1. 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. {{{ @@ -117, +116 @@ = Publishing = In 5 days if [[http://hadoop.apache.org/bylaws#Decision+Making|the release vote passes]], the release may be published. - + 1. In JIRA, "release" the version, setting the date to the end-of-vote date. Visit the "Administer Project" page, then the "Manage versions" page. You need to have the "Admin" role in HADOOP, HDFS, MAPREDUCE, and YARN. 1. Set environment variable version for later steps. {{{export version=X.Y.Z}}} 1. Tag the release. Do it from the release branch and push the created tag to the remote repository: {{{ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
