Info |
---|
Please do not edit this page. Content has been migrated to the new website being developed. Pull requests are welcome for the source there. |
This document describes the process to release Apache Ozone. The process is not yet scripted, and the documentation is a work in progress
...
- Build the Release Tarballs. Make sure that Hugo is installed so that this step will also build the documentation. Also make sure you are using GNU-tar instead of BSD-tar.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
mvn clean install -Dmaven.javadoc.skip=true -DskipTests -Psign,dist,src -Dtar -Dgpg.keyname="$CODESIGNINGKEY" |
...
- Link to the release candidate tag on Github
- Link to a Jira query showing all resolved issues for this release. Something like this.
- Location of the source and binary tarballs. This link will look something like https://dist.apache.org/repos/dist/dev/ozone/1.2.0-rc0/
- Location where the maven artifacts are staged. This link will look something like https://repository.apache.org/content/repositories/orgapacheozone-1001/
- Link to the public key used to sign the artifacts. This should always be in the KEYS file and you can just link to that: https://dist.apache.org/repos/dist/dev/ozone/KEYS
- Fingerprint of the key used to sign the artifacts.
...
The Ozone docker image is intended for testing purposes only, not production use. Therefore, it is ok to update this after announcing the release. An example pull request to update the docker image is here. The target branch for your pull request should be latest
. After the pull request is merged, it can be published to docker hub by fast-forwarding the ozone-latest
branch to match the latest
branch. Also, create a new branch named like ozone-1.5.0
(replace the version) and push it to GitHub.
Code Block | ||
---|---|---|
| ||
git checkout ozone-latest git pull git merge --ff-only origin/latest git checkout -b "ozone-${VERSION}" git push origin ozone-latest "ozone-${VERSION}" |
...