Google Git
Sign in
apache / yunikorn-release / refs/tags/v1.5.0-1
tag324bfa4325d2c09b381c88269c8d459ba69f2c96
taggerHuangTing-Yao <tingyao@apache.org>Wed Feb 28 17:03:47 2024 +0800
object6955da0eba3017031e6511d702f2942a7e86c575 
RC1 for v1.5.0
commit6955da0eba3017031e6511d702f2942a7e86c575[log] [tgz]
authorHuangTing-Yao <tingyao@apache.org>Wed Feb 28 17:03:10 2024 +0800
committerHuangTing-Yao <tingyao@apache.org>Wed Feb 28 17:03:10 2024 +0800
tree9b171ca2383abfc5eab8359b5732f5c5b344de57
parent7890ff103793b495e5908b81d6c4489e91b8f93a [diff]
Update helm chart version
1 file changed
tree: 9b171ca2383abfc5eab8359b5732f5c5b344de57
  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.