You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2018/07/19 10:37:00 UTC

[jira] [Commented] (SLING-7534) Release policy - stop providing MD5 signatures

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

Bertrand Delacretaz commented on SLING-7534:
--------------------------------------------

[~karlpauls] on the Felix list Raymond says you have investigated and found out that the md5 and sha1 files are generated in Nexus, can you confirm and do you have pointers that confirm that?

I'm asking because to me the discussion at [1] is not fully clear.

(and BTW I agree with Carsten that this is an ASF-wide issue, but haven't found a solution elsewhere so far)

[1] https://lists.apache.org/thread.html/c50e4842dbbe13b8196a43fa76d6040f8971bc5e812b561d080c5776@%3Cusers.infra.apache.org%3E

> Release policy - stop providing MD5 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
>
> 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
(v7.6.3#76005)