You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Weiwei Yang (Jira)" <ji...@apache.org> on 2021/07/26 16:33:00 UTC
[jira] [Commented] (YUNIKORN-764) Document how to verify a release
[ https://issues.apache.org/jira/browse/YUNIKORN-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17387468#comment-17387468 ]
Weiwei Yang commented on YUNIKORN-764:
--------------------------------------
hi [~yuchaoran2011], thanks for sharing the docs from flink. this is a good practice.
Right now, we are maintaining release-related docs here: [https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md.] I think it makes sense to move the doc to our website: [https://yunikorn.apache.org/docs/next/developer_guide/release.] Then we can cover docs for both release-managers (who helps to create a release) and developers (who helps to verify a release).
> Document how to verify a release
> --------------------------------
>
> Key: YUNIKORN-764
> URL: https://issues.apache.org/jira/browse/YUNIKORN-764
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: documentation
> Reporter: Chaoran Yu
> Assignee: Chaoran Yu
> Priority: Major
>
> We should document how a community member can go about verifying a release. For example, Flink has such a [page|https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release]. [https://yunikorn.apache.org/community/download/] already has some info about verifying the checksums and signature. But we also need info how to perform functionality checks
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org