You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2018/10/01 18:57:00 UTC

[jira] [Resolved] (UIMA-5856) Use modern checksum algorithms during release

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

Marshall Schor resolved UIMA-5856.
----------------------------------
    Resolution: Fixed

> Use modern checksum algorithms during release
> ---------------------------------------------
>
>                 Key: UIMA-5856
>                 URL: https://issues.apache.org/jira/browse/UIMA-5856
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test, Website
>            Reporter: Richard Eckart de Castilho
>            Assignee: Richard Eckart de Castilho
>            Priority: Major
>             Fix For: parent-pom-12
>
>
> Apache policy requires that we drop generating MD5 / SHA1 checksums and switch:
> – for new releases :
>  – you MUST supply a SHA-256 and/or SHA-512 file
>  – you SHOULD NOT supply MD5 or SHA-1 files
> See http://www.apache.org/dev/release-distribution#sigs-and-sums
> Best place to do this would be the parent-pom.
> Its a bit of a blocker for producing any new releases unless sub-projects override all the code-signing provisions in the UIMA parent pom.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)