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

Konrad Windszus edited comment on SLING-7534 at 5/5/21, 1:07 PM:
-----------------------------------------------------------------

With 
[https://github.com/apache/sling-parent/commit/d5590df5680dc569a8598918fa7fadfbe7bab975]
 we attach SHA-512 checksums as build artifacts (to upload to the Nexus Staging 
Repo and to ease pushing to dist)


was (Author: kwin):
With 
[https://github.com/apache/sling-parent/commit/d5590df5680dc569a8598918fa7fadfbe7bab975]
 we attach SHA-512 checksums to the build (to upload to the Nexus Staging Repo 
and to ease pushing to dist)

> Release policy - stop providing MD5 and start providing SHA-512 checksums
> -------------------------------------------------------------------------
>
>                 Key: SLING-7534
>                 URL: https://issues.apache.org/jira/browse/SLING-7534
>             Project: Sling
>          Issue Type: Task
>          Components: Tooling
>            Reporter: Robert Munteanu
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Parent 42
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> See http://www.apache.org/dev/release-distribution#sigs-and-sums , we SHOULD 
> no longer provide MD5 checksums for new releases.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to