[ 
https://issues.apache.org/jira/browse/THRIFT-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jens Geyer resolved THRIFT-6381.
--------------------------------
      Assignee: Sylwester Lachiewicz
    Resolution: Fixed

> Publish sha256 and sha512 checksums for releases instead of md5 and sha1
> ------------------------------------------------------------------------
>
>                 Key: THRIFT-6381
>                 URL: https://issues.apache.org/jira/browse/THRIFT-6381
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Sylwester Lachiewicz
>            Assignee: Sylwester Lachiewicz
>            Priority: Minor
>             Fix For: 0.26.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> [doc/ReleaseManagement.md|https://github.com/apache/thrift/blob/master/doc/ReleaseManagement.md]
>  has the release manager create {{.md5}}, {{.sha1}} and {{.sha256}} files, 
> and the vote mail template lists all three. [ASF release distribution 
> policy|https://infra.apache.org/release-distribution.html#sigs-and-sums] says 
> a new release must supply SHA-256 and/or SHA-512 and should not supply MD5 or 
> SHA-1. The guide should generate {{.sha256}} and {{.sha512}} and the 
> templates list those two. Existing releases do not need new files.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to