THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Extract the contents of the source tarball and build it with an empty maven cache by renaming your
~/.m2
directory before doing the build. - Check the size of the output binary tarball for significant size increase from the last release.
- The Apache servers currently have a limit of 350mb for release artifacts.
- A significant increase in size could indicate a dependency issue that needs to be fixed.
- The Apache svn repo has a size limit for release artifacts. If uploading svn fails because the tarball is too big, we need to contact INFRA to increase our repo size. See here for details.
- Verify signatures
- Download the KEYS file from https://dist.apache.org/repos/dist/release/ozone/KEYS
- Import its contents (which should include your public gpg key):
gpg --import KEYS
- Verify each .tar.gz artifact:
gpg --verify <artifact>.tar.gz.asc <artifact>.tar.gz
- Verify checksums
- Run
shasum -a 512 *.tar.gz
- Verify that the output checksums for each artifact match the contents of its .sha512 file and the SHA512 line in its .mds file.
- Run
- Make sure docs are present in the release tarball
- There should be a directory called docs in the top level. If there is not, then
hugo
was not installed during the build and it must be re-done. - Extract the release and open docs/index.html in your web browser, and check that the documentation website looks ok.
- There should be a directory called docs in the top level. If there is not, then
- Check the output of running
bin/ozone version
from the extracted release tarball- After extracting the release, the output of this command should contain:
- The correct release
- The correct national park tag
- A non-snapshot version of Ratis.
- A link to the apache/ozone GitHub repository (not your fork).
- The git hash of the last commit the release was built on.
- After extracting the release, the output of this command should contain:
- Run the Ozone upgrade acceptance tests by running
test.sh
from the compose/upgrade directory in the extracted release tarball.- This check is also run by the GitHub actions CI for each commit, so it should pass with no surprises.
...