You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2020/08/19 07:30:00 UTC

[jira] [Resolved] (YUNIKORN-370) Branch release repo for helm chart versioning

     [ https://issues.apache.org/jira/browse/YUNIKORN-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wilfred Spiegelenburg resolved YUNIKORN-370.
--------------------------------------------
    Fix Version/s: 0.9
       Resolution: Fixed

All changes have been made. Release v0.9.0 has been created and pushed for a vote.

Further optimisations for the release tool to follow in seperate jiras.

> Branch release repo for helm chart versioning
> ---------------------------------------------
>
>                 Key: YUNIKORN-370
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-370
>             Project: Apache YuniKorn
>          Issue Type: New Feature
>          Components: release
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Major
>             Fix For: 0.9
>
>
> Helm charts can be different for releases. There is currently no way to generate versions or commit new functionality without affecting existing releases.
> The repos must be branched for a release.
> For the v0.9.0 release this includes rolling back YUNIKORN-265 and YUNIKORN-346 from the branch
> For the master this involves the roll back of the staged 0.9.0 chart.
> As a side:
> - Clean up script and config to not generate file names with RC in the name for the release candidates.
> - remove .DS_store file



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org