THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Verify that the release bits were correctly generated. These steps don't check for release functionality.
- Verify pgp signaturessignatures using the instructions at https://www.apache.org/info/verification.html#CheckingSignatures. You will need GPG installed. On MacOS machines, you can install GPG with HomeBrew using
brew install gpg
. Verify checkums for the source and binary artifacts from the corresponding .mds files. E.g. a quick way to do so using gpg is:
Code Block language bash theme RDark gpg --print-mds hadoop-3.1.1-src.tar.gz > mds.tmp diff hadoop-3.1.1-src.tar.gz.mds mds.tmp
- Verify that there are no MD5 signatures provided.
- Verify that jars have been correctly staged to repository.apache.org.
- For 3.x releases and later, verify that the shaded fat jars look correct.
- Sanity check the CHANGES.md and RELEASENOTES.md files.
- Verify that source and binary tarballs include LICENSE.txt and NOTICE.txt files.
...
- Extract the source tarball and build the release from sources using:
mvn clean install package -Pdist -DskipTests=true
The binary tarball will be available at hadoop-dist/target/hadoop-<version>.tar.gz.
- Follow all the steps from the Verify Binary Release section below.
Verify that the source distribution has no extra files/changes by diffing against the git tag in a local clone of the Hadoop repo. E.g.
Code Block language bash theme RDark $ git checkout release-3.1.0-RC1 $ diff -r $PWD /tmp/hadoop-3.1.0 # Assuming RC src tarball was unpacked in /tmp/hadoop-3.1.0
Verify Binary Release Bits
...
Page properties | ||
---|---|---|
| ||
|