Oh! As an added bonus of migrating to proper bintray package repository
types, we also cure the pain of users attempting to install older
versions than the latest release, since all versions in the suite are
installable.
--
Michael
On 10/17/19 9:47 AM, Michael Shuler wrote:
Noted:
https://issues.apache.org/jira/browse/CASSANDRA-14963
Fundamental current docker build flaws:
https://issues.apache.org/jira/browse/CASSANDRA-14962
Distribution changes suggested for deb/rpm:
https://issues.apache.org/jira/browse/CASSANDRA-14966
https://issues.apache.org/jira/browse/CASSANDRA-14967
..which are dependencies of repository sig changes to solve the whole
KEYS file pain for package users, for ever and ever:
https://issues.apache.org/jira/browse/CASSANDRA-14968
There are other ASF projects using bintray metatdata signing (the repo
metadata is *not* a release artifact). Artifact sigs uploaded to /dist/
and subsequent verification from KEYS seem orthogonal to repo metadata
signatures to me. I don't see why we cannot do the same as quite a few
other projects and use automated bintray repo signing, migrating to
appropriate bintray repository types.
I believe some basic distribution changes would greatly help the entire
question here, including making release builds easier for other people
to perform, shortening the cycle times as desired. If there is some
interest in building releases, I would like some help solving the
problems that exist and have been in JIRA for quite some time.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
