You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (JIRA)" <ji...@apache.org> on 2018/04/04 19:34:00 UTC
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with
our artifacts
[ https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426070#comment-16426070 ]
Jan Høydahl commented on LUCENE-7935:
-------------------------------------
Looks like a mismatch here, the maven artifacts build still produces md5 and sha1 files, while the smoke tester tries to verify sha512.
I suppose we want to discontinue md5 also for all maven artifacts, or is it required?
> Release .sha512 hash files with our artifacts
> ---------------------------------------------
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts, and we also include {{.sha1}} files. It is expected that {{.sha512}} will be required in the future (see https://www.apache.org/dev/release-signing.html#sha1), so why not start generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org