You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2017/12/15 01:46:00 UTC

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

     [ https://issues.apache.org/jira/browse/TIKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Allison resolved TIKA-2528.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.18
                   2.0

[~sebb@apache.org], thank you, again.

I moved our KEYS file for 1.17, and I added documentation on our release process wiki:

1) to copy the KEYS file to https://dist.apache.org/repos/dist/dev/tika/
2) Change the announcement to point to the download page.

I've only signed Tika with one key, my current one, so there's no action on my part there.

> 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
>             Fix For: 2.0, 1.18
>
>
> 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- Same key I'm using now...if anyone else needs to add a key, please do.
> Other areas for improvement in our announce/release process?



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