cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Shuler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12239) Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
Date Mon, 22 Aug 2016 20:49:21 GMT

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

Michael Shuler commented on CASSANDRA-12239:
--------------------------------------------

Set as blocker on 3.8 release.

> 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)

Mime
View raw message