[
https://issues.apache.org/jira/browse/RANGER-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410772#comment-16410772
]
Velmurugan Periasamy commented on RANGER-2028:
----------------------------------------------
Thanks [~zsombor].
Cherry picked into ranger-1.0 as well.
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=f4427158867925affd5cfb49190b94873bea7626]
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=d8a0e1072c95a0955475a97dba79833f72e77d2e]
> Fix release build scripts to conform to latest Apache release guidelines
> ------------------------------------------------------------------------
>
> Key: RANGER-2028
> URL: https://issues.apache.org/jira/browse/RANGER-2028
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Colm O hEigeartaigh
> Assignee: Velmurugan Periasamy
> Priority: Major
> Fix For: 1.1.0, 1.0.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)
