Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-5143

rm or formalize dealing with "general" KEYS files in our dist dir

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.5, master (8.0)
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      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

        Attachments

        1. LUCENE-5143-reopen-smoke.patch
          12 kB
          Jan Høydahl
        2. LUCENE-5143-reopen-smoke.patch
          9 kB
          Jan Høydahl
        3. LUCENE-5143.patch
          4 kB
          Jan Høydahl
        4. verify.sh
          2 kB
          Jan Høydahl
        5. KEYS
          280 kB
          Jan Høydahl
        6. verify.sh
          2 kB
          Jan Høydahl
        7. KEYS
          277 kB
          Jan Høydahl
        8. KEYS
          277 kB
          Jan Høydahl
        9. verify.log
          11 kB
          Jan Høydahl
        10. verify.sh
          2 kB
          Jan Høydahl
        11. KEYS
          270 kB
          Jan Høydahl
        12. LUCENE-5143_READMEs.patch
          9 kB
          Jan Høydahl
        13. LUCENE_5143_KEYS.patch
          401 kB
          Jan Høydahl
        14. LUCENE-5143.patch
          5 kB
          Jan Høydahl
        15. LUCENE-5143.patch
          3 kB
          Jan Høydahl
        16. LUCENE-5143_READMEs.patch
          9 kB
          Jan Høydahl
        17. LUCENE-5143.patch
          2 kB
          Jan Høydahl
        18. LUCENE-5143_READMEs.patch
          9 kB
          Jan Høydahl

          Issue Links

            Activity

              People

              • Assignee:
                janhoy Jan Høydahl
                Reporter:
                hossman Hoss Man
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: