Google Git
Sign in
apache/yunikorn-release/refs/tags/v1.6.0-1
tag
7ac3cf420776b50c554be185170d8c3d27c367e3
tagger
Peter Bacsko <bacskop@gmail.com>
Wed Sep 11 18:08:29 2024 +0200
object
e1648559657575b56b0e3f7176afef4cfef19740
RC1 for 1.6.0
commit
e1648559657575b56b0e3f7176afef4cfef19740
[log] [tgz]
author
Peter Bacsko <bacskop@gmail.com>
Tue Sep 10 15:41:12 2024 +0200
committer
Peter Bacsko <bacskop@gmail.com>
Wed Sep 11 13:04:25 2024 +0200
tree
e8eb3c924196f424c5fb0cfc19e5edb4e90ac6d6
parent
8d598a1cc23dc23477863094d918ebbe02edc489 [diff]
Update CHANGELOG for 1.6.0
1 file changed
tree: e8eb3c924196f424c5fb0cfc19e5edb4e90ac6d6
  1. .github/
  2. helm-charts/
  3. perf-tools/
  4. release-top-level-artifacts/
  5. tools/
  6. .asf.yaml
  7. .gitignore
  8. check_license.sh
  9. go.mod
  10. go.sum
  11. LICENSE
  12. NOTICE
  13. README.md
README.md

Apache YuniKorn Release

pre-commit

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.