[
https://issues.apache.org/jira/browse/YUNIKORN-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727688#comment-17727688
]
Craig Condit commented on YUNIKORN-1759:
----------------------------------------
Hi [~Yukali], wanted to give you a heads up - we've got a bit of an issue here.
Because yunikorn-scheduler-interface was tagged initially as v1.3.0 (and
referenced from the yunikorn-core PR), that version is now cached forever by
https://proxy.golang.org (the default GOPROXY). This means that if we end up
deploying a different build of that module, we've now got a broken YuniKorn
1.3.0 release. I suspect the SI will not need to change before release, but
this illustrates why we need to be very careful about tagging. If this had
happened on yunikorn-core, yunikorn-k8shim, or yunikorn-web, it would be
impossible to release a proper 1.3.0 release (and we'd likely need to burn that
version and go with 1.3.1 instead).
> helm chart release v1.3
> -----------------------
>
> Key: YUNIKORN-1759
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1759
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: release
> Reporter: Wilfred Spiegelenburg
> Assignee: Chen Yu Teng
> Priority: Major
> Labels: pull-request-available
>
> Release the helm charts in yunikorn-release repository with following steps:
> * tag v1.3 and upload charts
> * update version to v1.3 in charts
> * check supported k8s versions in charts
> * add v1.3 to index.yaml (gh-pages)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
