Hey folks, In an effort to document/automate validiting the release, I noticed that GPG picked a more recent key for me, which is an ECC key, not RSA, which it seems will break things if we have it in the KEYS file, so I'm going to close this proposed release/vote, re-release it with my RSA key, and re-call for the vote along with a handy script to pull down the artifacts and check the sha1/md5/gpg signatures you can run.
Thanks, Doug > On Oct 7, 2025, at 5:56 PM, Doug Rohrer <[email protected]> wrote: > > Hey folks, > > I'd like to propose a new release of the dtest-api that includes some updates > to make it easier for Cassandra maintainers to deal with some of the jmx > support classes, and for external consumers of the dtest api to use the jmx > client without having to jump through some somewhat ugly hoops. > > Repository: > https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git > > Candidate SHA: > https://github.com/apache/cassandra-in-jvm-dtest-api/commit/421fe11b8fd862d82f89607c1ae2807657ba6578 > Tagged with 0.0.18 > > Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1419/org/apache/cassandra/dtest-api/0.0.18/ > > Key signature: 2C94EBA59C0BA7E0EDAAE142BF79EF32B05FB5CA > > Changes since last release: > > * CASSANDRA-20884 - Move JMX classes to the in-jvm-dtest API project > > I have patches available for 4.0, 4.1, 5.0, and trunk Cassandra branches to > take advantage of these changes as well, which can be updated to use this > release and committed once the vote passes. > > The vote will be open for 72 hours. Everyone who has tested the build lis > invited to vote. Votes by PMC members are considered binding. A vote passes > if there are at least three binding +1s. > > See https://issues.apache.org/jira/browse/CASSANDRA-20884 for branches of > Cassandra for testing the dtest-api change (which currently use a snapshot > build of this). > > Thanks, > > Doug Rohrer >
