taverna-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stian Soiland-Reyes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAVERNA-875) Spurious file: KEYS.template; KEYS file must contain all used keys
Date Thu, 10 Dec 2015 09:55:10 GMT

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

Stian Soiland-Reyes commented on TAVERNA-875:
---------------------------------------------

I'm leaving the issue open as http://taverna.incubator.apache.org/community/releasing#gpg-keys
must be updated.

> Spurious file: KEYS.template; KEYS file must contain all used keys
> ------------------------------------------------------------------
>
>                 Key: TAVERNA-875
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-875
>             Project: Apache Taverna
>          Issue Type: Bug
>         Environment: https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS.template
>            Reporter: Sebb
>            Assignee: Stian Soiland-Reyes
>
> The KEYS.template file does not belong on the ASF mirrors.
> Also it suggests that the KEYS file is being automatically created from the file https://people.apache.org/keys/group/taverna.asc
> This is not advisable, because that file only contains current keys for current PPMC
members.
> The KEYS file is also needed to check archived releases, so must contain all the keys
which have ever been used to sign a release.
> Note also that following graduation, the taverna.asc file will only contain current keys
of current PMC members. However signers can include committers who are not PMC members.
> Please can you remove the KEYS.template file, and ensure that the KEYS file is maintained
as described below in future, thanks:
> http://www.apache.org/dev/release-signing#keys-policy



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message