[
https://issues.apache.org/jira/browse/YUNIKORN-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556140#comment-17556140
]
Wilfred Spiegelenburg commented on YUNIKORN-1215:
-------------------------------------------------
To clarify: we *must* not post any releases tagged {{{}latest{}}}. Two things:
* A release *must* be voted on and the content is set. That would not be the
case for a release which is tagged with latest. It is even part of the official
Apache release policy:
https://www.apache.org/legal/release-policy.html#compiled-packages
* The latest tag is ambiguous specially when we have multiple branches in
development. Does it change when we release 1.0.1 after we release 1.1 or not?
It was released latest but in semver it is not.
> Enable multi-arch release builds
> --------------------------------
>
> Key: YUNIKORN-1215
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1215
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: release
> Reporter: Craig Condit
> Assignee: Wilfred Spiegelenburg
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> Currently, we provide convenience Docker images for amd64 based off our
> official release sources. It would be nice to be able to offer multi-arch
> images containing both amd64 and arm64.
> However, one challenge is that per Apache release policy, builds need to be
> done on hardware the release manager controls...
> We can use this JIRA as a place to discuss options / alternatives, etc.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
