Google GitGoogle Git
Sign in
apache/yunikorn-release/9f4f71d7b43f7b8fa4e1728d254ce44e3032f890
commit
9f4f71d7b43f7b8fa4e1728d254ce44e3032f890
[log]
author
Wilfred Spiegelenburg <wilfreds@apache.org>
Tue Nov 14 12:08:12 2023 +1100
committer
Wilfred Spiegelenburg <wilfreds@apache.org>
Tue Nov 14 12:08:12 2023 +1100
tree
c40fa8374d4466344b802a231f24cc57b20b907f
parent
1b064b963a8b9fab4d1015e73da3b1339fdc0c55 [diff]
[YUNIKORN-2095] Sync gRPC releases (#162)

Update gRPC to the same as all other repos
Fix lagging dependencies gotest and base go lang dependencies with CVEs
logged against it.

Closes: #162

Signed-off-by: Wilfred Spiegelenburg <wilfreds@apache.org>
3 files changed
tree: c40fa8374d4466344b802a231f24cc57b20b907f
  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.