[jira] [Issue Comment Deleted] (CASSANDRA-12239) Add mshuler's key FE4B2BDA to dist/cassandra/KEYS

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

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

Brandon Williams updated CASSANDRA-12239:
-----------------------------------------
    Comment: was deleted

(was: {noformat}
< driftx> all I know is he tried his committer creds, they didn't work, and I was out of ideas
< jfarrell> dist.a.o is for PMC to push to, we do not have committers_may_release set
< driftx> ah, I see.
{noformat}

[~tjake] will have to help you out, it seems.)

> Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
> -------------------------------------------------
>
>                 Key: CASSANDRA-12239
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12239
>             Project: Cassandra
>          Issue Type: Task
>          Components: Packaging
>            Reporter: Michael Shuler
>            Assignee: Michael Shuler
>            Priority: Blocker
>             Fix For: 3.8
>
>         Attachments: KEYS+mshuler.diff.txt
>
>
> I've started working on packaging with the 3.8 release and signed the staging artifacts with FE4B2BDA. This key will need to be added for the debian repository signature to function correctly, if it's released as-is, or perhaps [~tjake] will need to re-sign the release. Users will need to also fetch this new key and add to {{apt-key}}.
> {{KEYS}} patch attached.
> Assigned to myself, but I am not sure exactly where {{KEYS}} lives - in svn somewhere or a direct upload? :)



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