You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2020/10/05 13:40:00 UTC
[jira] [Comment Edited] (SLING-7534) Release policy - stop
providing MD5 and start providing SHA-512 checksums
[ https://issues.apache.org/jira/browse/SLING-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208086#comment-17208086 ]
Konrad Windszus edited comment on SLING-7534 at 10/5/20, 1:39 PM:
------------------------------------------------------------------
Due to performance reasons SHA512/256 won't ever be generated/uploaded by default in Maven (MRESOLVER-140). Therefore we have to use a dedicated plugin to generate SHA512, but currently this has poor support for uploading it to the Stage repository. For details look at https://github.com/apache/sling-parent/pull/10
was (Author: kwin):
Due to performance reasons SHA512/256 won't ever be generated/uploaded by default in Maven (MRESOLVER-130). Therefore we have to use a dedicated plugin to generate SHA512, but currently this has poor support for uploading it to the Stage repository. For details look at https://github.com/apache/sling-parent/pull/10
> 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 40
>
> Time Spent: 1h 40m
> 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)