You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Andrea Tarocchi (Jira)" <ji...@apache.org> on 2020/05/17 13:19:00 UTC
[jira] [Issue Comment Deleted] (SLING-7534) Release policy - stop
providing MD5 and start providing SHA-512 signatures
[ https://issues.apache.org/jira/browse/SLING-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Tarocchi updated SLING-7534:
-----------------------------------
Comment: was deleted
(was: Is there any update on this one? It is, I believe a common problem throughout all the projects.
Releasing a project with ~300 artifacts is simply not feasible with sha512 verified and added "manually".)
> Release policy - stop providing MD5 and start providing SHA-512 signatures
> --------------------------------------------------------------------------
>
> Key: SLING-7534
> URL: https://issues.apache.org/jira/browse/SLING-7534
> Project: Sling
> Issue Type: Task
> Components: Tooling
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Parent 40
>
>
> 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)