Google Git
Sign in
apache / yunikorn-release / 6b852b907d7dd6e815c418fb110a04b6b23db3b5
commit6b852b907d7dd6e815c418fb110a04b6b23db3b5[log] [tgz]
authorTingyao <tingyao@apache.org>Mon Sep 12 15:52:55 2022 +0200
committerPeter Bacsko <pbacsko@cloudera.com>Mon Sep 12 15:52:55 2022 +0200
treeccc380339921da55a4835cec048eb12eaf43727d
parentff2e25cc0928d8ced98ee722b6c660ad64ba1abe [diff]
[YUNIKORN-1308] validate_cluster.sh should auto-detect DOCKER_ARCH (#109)

Closes: #109

Signed-off-by: Peter Bacsko <pbacsko@cloudera.com>
2 files changed
tree: ccc380339921da55a4835cec048eb12eaf43727d
  1. helm-charts/
  2. perf-tools/
  3. release-top-level-artifacts/
  4. tools/
  5. .asf.yaml
  6. .gitignore
  7. go.mod
  8. go.sum
  9. LICENSE
  10. NOTICE
  11. README.md
README.md

Apache YuniKorn Release

This project provides the instructions and tools needed to generate Apache YuniKorn release artifacts. Reference:

Release Procedure

A simplified procedure:

  • Create a release branch in all git repos, such as branch-0.8
  • Stabilize the release
  • Create a tag and prepare to generate the release, e.g v0.8.0
  • Run the release tool to generate source code tarball, checksum and signature
  • Upload tarball, signature and checksum as a release candidate
  • Start a voting thread for the project
  • Publish the release (source code, helm chart and pre-build images)
  • Update the website

The full procedure is documented in the release procedure.