[
https://issues.apache.org/jira/browse/CASSANDRA-12239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488357#comment-15488357
]
Michael Shuler commented on CASSANDRA-12239:
--------------------------------------------
As a quick additional check, I don't see anything odd about my local info:
{noformat}
mshuler@hana:~/svn/cassandra-dist$ svn info
Path: .
Working Copy Root Path: /home/mshuler/svn/cassandra-dist
URL: https://dist.apache.org/repos/dist/release/cassandra
Relative URL: ^/release/cassandra
Repository Root: https://dist.apache.org/repos/dist
Repository UUID: 0d268c88-bc11-4956-87df-91683dc98e59
Revision: 15353
Node Kind: directory
Schedule: normal
Last Changed Author: jake
Last Changed Rev: 14277
Last Changed Date: 2016-07-05 09:39:33 -0500 (Tue, 05 Jul 2016)
{noformat}
https://www.apache.org/dev/version-control.html#commit-403 says ask the PMC to
check authz and LDAP/Unix group memebership. Could someone help out with this
check?
> 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)
