lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Commented] (LUCENE-5143) rm or formalize dealing with "general" KEYS files in our dist dir
Date Tue, 28 Feb 2017 14:53:45 GMT


Jan Høydahl commented on LUCENE-5143:

Ah, thanks :)

I think we should stop copying this file to KEYS - see the last chapter of this page
- it says explicitly that it cannot be used as-is for a KEYS file since it will not contain
all needed keys.

So if we agree that we do not need KEYS file for each version release, only one on top-level,
then we can add to the Release TODO a bullet about checking that your own key is in the current
KEYS file, and if not add it. It should be sufficient, since we only require keys of committers
who have signed a release, so an RM who has done a release simply needs to verify that his
current key is on the list.

> 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
> 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