lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Updated] (LUCENE-5143) rm or formalize dealing with "general" KEYS files in our dist dir
Date Mon, 21 Aug 2017 07:49:00 GMT


Jan Høydahl updated LUCENE-5143:
    Attachment: LUCENE-5143_READMEs.patch

Updated README patch to also discuss .sha512 hash.

> rm or formalize dealing with "general" KEYS files in our dist dir
> -----------------------------------------------------------------
>                 Key: LUCENE-5143
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Hoss Man
>         Attachments: LUCENE-5143.patch, LUCENE-5143_READMEs.patch, LUCENE-5143_READMEs.patch
> At some point in the past, we started creating a snapshots of KEYS (taken from the auto-generated
data from in the release dir of each release...
> etc...
> But we also still have some "general" KEYS files...
> ...which (as i discovered when i went to add my key to them today) are stale and don't
seem to be getting updated.
> I vaguely remember someone (rmuir?) explaining to me at one point the reason we started
creating a fresh copy of KEYS in each release dir, but i no longer remember what they said,
and i can't find any mention of a reason in any of the release docs, or in any sort of comment
> we probably do one of the following:
>  * remove these "general" KEYS files
>  * add a disclaimer to the top of these files that they are legacy files for verifying
old releases and are no longer used for new releases
>  * ensure these files are up to date stop generating per-release KEYS file copies
>  * update our release process to ensure that the general files get updated on each release
as well

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message