You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metamodel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/26 05:51:00 UTC

[jira] [Commented] (METAMODEL-1193) Update release build to create sha512 files instead of md5+sha1

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

ASF GitHub Bot commented on METAMODEL-1193:
-------------------------------------------

Github user kaspersorensen commented on the issue:

    https://github.com/apache/metamodel/pull/186
  
    Fixed a typo: This fix is for METAMODEL-1193, not METAMODEL-1116.


> Update release build to create sha512 files instead of md5+sha1
> ---------------------------------------------------------------
>
>                 Key: METAMODEL-1193
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-1193
>             Project: Apache MetaModel
>          Issue Type: Task
>            Reporter: Kasper Sørensen
>            Priority: Major
>
> The ASF's release guidelines have changed and we should no longer be producing the SHA1 and MD5 files. Instead we should be producing either SHA256 or SHA512 files. I suggest SHA512 just to use the best of the two options.
> To fix this story: Update our POM file(s) to ensure that .sha512 (or .sha256 is there is a good reason for it) files during a release build.



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