You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Velmurugan Periasamy (JIRA)" <ji...@apache.org> on 2018/10/04 19:12:00 UTC
[jira] [Commented] (RANGER-2241) Fix release build scripts to
conform to latest Apache release guidelines - Part 2 - Remove sha1
[ https://issues.apache.org/jira/browse/RANGER-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638716#comment-16638716 ]
Velmurugan Periasamy commented on RANGER-2241:
----------------------------------------------
SHA1 also needs to be removed (in addition to MD5).
> Fix release build scripts to conform to latest Apache release guidelines - Part 2 - Remove sha1
> -----------------------------------------------------------------------------------------------
>
> Key: RANGER-2241
> URL: https://issues.apache.org/jira/browse/RANGER-2241
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Colm O hEigeartaigh
> Assignee: Velmurugan Periasamy
> Priority: Major
> Fix For: 1.0.1, 2.0.0, 1.1.1, 1.2.1
>
>
> Fix the release build scripts to conform to the Apache release guidelines surrounding hashes:
> [http://www.apache.org/dev/release-distribution#sigs-and-sums]
> The names of signature and checksum files MUST be formed by adding to the
> name of the artifact the following suffixes:
> - .asc for a (ASCII armored) PGP signature
> - .sha1 for a SHA-1 checksum
> - .sha256 for a SHA-256 checksum
> - .sha512 for a SHA-512 checksum
> - .md5 for a MD5 checksum
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)