You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/06/24 21:43:00 UTC
[jira] [Updated] (HBASE-24572) do-release vote template should
include the fingerprint of the gpg key used to sign the release
[ https://issues.apache.org/jira/browse/HBASE-24572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk updated HBASE-24572:
---------------------------------
Summary: do-release vote template should include the fingerprint of the gpg key used to sign the release (was: do-release vote template should include the fingerprint of the gpg key used to signe the release)
> do-release vote template should include the fingerprint of the gpg key used to sign the release
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-24572
> URL: https://issues.apache.org/jira/browse/HBASE-24572
> Project: HBase
> Issue Type: Task
> Components: build, community
> Reporter: Nick Dimiduk
> Priority: Major
>
> Right now the template us substituting the release manager's email address in for the variable {{GPG_KEY}}. I think it doesn't hurt to make note of the email address, but what we really want here is the key's fingerprint, or some meaningly identifiable portion of it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)