You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2018/12/01 03:59:00 UTC
[jira] [Commented] (DERBY-6973) Provide SHA-512 checksums on future
releases
[ https://issues.apache.org/jira/browse/DERBY-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16705613#comment-16705613 ]
Bryan Pendleton commented on DERBY-6973:
----------------------------------------
I agree, we shouldn't mess with the Maven checksums.
I can cross-check the Linux and Windows checksums as we get closer to the release; please re-remind me as part of our release candidate vetting. :)
> Provide SHA-512 checksums on future releases
> --------------------------------------------
>
> Key: DERBY-6973
> URL: https://issues.apache.org/jira/browse/DERBY-6973
> Project: Derby
> Issue Type: Bug
> Components: Web Site
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2, 10.8.3.0, 10.9.1.0, 10.10.1.1, 10.10.2.0, 10.11.1.1, 10.12.1.1, 10.13.1.1, 10.14.1.0, 10.15.0.0
> Reporter: Warren MacEvoy
> Assignee: Rick Hillegas
> Priority: Major
> Fix For: 10.15.0.0
>
> Attachments: derby-6973-01-aa-useSHA512.diff
>
>
> Releases have md5 sum for signatures, and nothing modern. How is this even possible?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)