[jira] [Commented] (TIKA-2528) Fix key location, keys file and download link

["Sebb (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TIKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290912#comment-16290912 ] 

Sebb commented on TIKA-2528:
----------------------------

Note that you don't need to add all the Tika keys to the KEYS file; just the ones used to sign releases.

If a new Release Manager produces an RC, probably best to add their key at that point so the proper KEYS file can be used in the VOTE mail.
It does not matter if one or two keys end up being unused (if the RC fails), but if all PMC keys are added that makes the file harder to maintain.

Remember that keys should not be removed (*) from the file if they have been used for a release.

(*) If a key is compromised and has to be revoked then I guess it would be best to remove the key and note it in the file. Ask Infra for advice.

> Fix key location, keys file and download link
> ---------------------------------------------
>
>                 Key: TIKA-2528
>                 URL: https://issues.apache.org/jira/browse/TIKA-2528
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Tim Allison
>            Priority: Minor
>
> Thanks to [~sebb@apache.org] for pointing out areas for improvement in our release process: https://lists.apache.org/thread.html/3ca68b758fea4dbc890d5d600590b680a1fe745fe7bd559e7e19789e@%3Cdev.tika.apache.org%3E
> 1) Change link in announcement email to http://tika.apache.org/download.html
> 2) Move keys to the standard link: https://www.apache.org/dist/tika/KEYS
> 3) At the least, I need to add back my 1.15 release key
> Other areas for improvement in our announce/release process?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)