You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Kouhei Sutou (JIRA)" <ji...@apache.org> on 2019/04/03 21:42:00 UTC

[jira] [Commented] (ARROW-5107) [Release] Validate non-RC source and binary artifacts

    [ https://issues.apache.org/jira/browse/ARROW-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809293#comment-16809293 ] 

Kouhei Sutou commented on ARROW-5107:
-------------------------------------

This is {{verify-release-cndidate.sh}}. So adding support for release (not candidate) is odd.
It's OK to me that we rename {{verify-release-candidate.sh}} to {{verify-release.sh}} and it supports both release and release candidate.

> [Release] Validate non-RC source and binary artifacts
> -----------------------------------------------------
>
>                 Key: ARROW-5107
>                 URL: https://issues.apache.org/jira/browse/ARROW-5107
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Krisztian Szucs
>            Priority: Major
>
> The release verification script has the following signature:
>  {{dev/release/verify-release-candidate.sh source|binaries X.Y.Z RC}}
> Which makes it impossible to verify actual (non-rc) releases.
> It could be useful to test already released artifacts, like:
> {{dev/release/verify-release-candidate.sh source|binaries X.Y.Z}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)