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 2017/03/08 00:46:38 UTC
[jira] [Commented] (LUCENE-5143) rm or formalize dealing with
"general" KEYS files in our dist dir
[ https://issues.apache.org/jira/browse/LUCENE-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900478#comment-15900478 ]
Jan Høydahl commented on LUCENE-5143:
-------------------------------------
So what do people think about the README.html changes?
I think perhaps we should use the KEYS files from the sub folders (solr/KEYS, java/KEYS, pylucene/KEYS) and remove the topmost one? Or should solr/lucene instead share the one topmost /KEYS file?
Regarding the buildAndPushRelease changes, I think there should also be an offline mode that will either skip verification or verify against a local dist checkout.
So the next step would be to commit these patches and then commit a consolidated KEYS file (or two identical in java/ and solr/).
> rm or formalize dealing with "general" KEYS files in our dist dir
> -----------------------------------------------------------------
>
> Key: LUCENE-5143
> URL: https://issues.apache.org/jira/browse/LUCENE-5143
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Hoss Man
> Attachments: LUCENE-5143.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 id.apache.org) in the release dir of each release...
> http://www.apache.org/dist/lucene/solr/4.4.0/KEYS
> http://www.apache.org/dist/lucene/java/4.4.0/KEYS
> http://archive.apache.org/dist/lucene/java/4.3.0/KEYS
> http://archive.apache.org/dist/lucene/solr/4.3.0/KEYS
> etc...
> But we also still have some "general" KEYS files...
> https://www.apache.org/dist/lucene/KEYS
> https://www.apache.org/dist/lucene/java/KEYS
> https://www.apache.org/dist/lucene/solr/KEYS
> ...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 in buildAndPushRelease.py
> 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org