Re: Who should be in our distribution KEYS file?

Sorry, I forgot to include the most important feature for potentially using bintray deb/rpm repos, signed by the bintray key: - New gpg keys could be added to KEYS for interested new release managers, and releases could be done by those interested new Cassandra release managers, requiring only

Re: Who should be in our distribution KEYS file?

For Debian, Fedora, etc. to package Cassandra at the OS level, first all dependencies (and deps of deps) must be packaged and uploaded, so they can be depended on by Cassandra. This means Hadoop. It has been attempted and abandoned by multiple people, myself included. A little digging on one

[JIRA Epic] Removing Contributor Role

In discussing this aspect of the change with ASF Infra, Gavin McDonald asked for a reconsideration. Firstly, he was concerned about Jira struggling under the load of auto-populating 12 user names. He suggested waiting until they have migrated users to LDAP later this year. Given Jira’s

[GitHub] asfgit closed pull request #8: Update URLs for gitbox.apache.org migration

asfgit closed pull request #8: Update URLs for gitbox.apache.org migration URL: https://github.com/apache/cassandra-builds/pull/8 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a

Re: Who should be in our distribution KEYS file?

If creating native deb/rpm package signatures and repo metadata signatures is the only issue that stops us from releasing more often and sharing the burden in doing so, then I'd be happy to discuss dropping this altogether. We can always distribute binary packages along with checksums and a

Re: Git Repo Migration

This migration is done, you'll need to update your git remotes like: git remote set-url origin https://gitbox.apache.org/repos/asf/cassandra.git Committers, you'll need to link your github and apache accounts via htts://gitbox.apache.org to get push access. Thanks, Sam > On 9 Jan 2019, at

Re: Git Repo Migration

https://issues.apache.org/jira/browse/INFRA-17593 Thanks, Sam > On 4 Jan 2019, at 21:43, Jonathan Haddad wrote: > > Great news, we can also remove this line: We cannot merge or close any pull > requests opened for the apache/cassandra