Re: [VOTE] Release dtest-api 0.0.18

[Doug Rohrer]

Yup - figured given all of us, even if we work on Cassandra for work, aren't 
necessarily glued to the dev list, so a gentle ping seemed appropriate, and 
thanks for voting!

I assume any vote (especially in a subproject) is likely to need a nudge here 
and there.

Doug

> On Oct 21, 2025, at 10:08 AM, Michael Shuler  wrote:
> 
> Also, thanks for the nudge - that triggered my attention. "At least 72 hours" 
> is the way. The number of sub-projects means less concentrated attention, so 
> do call it out if you need eyeballs and votes to get to the goal.
> 
> Kind regards,
> Michael
> 
> On 10/15/25 08:25, Doug Rohrer wrote:
>> Thanks to everyone for validating the release - the vote passes with 5 
>> Binding and 4 non-binding +1s.
>> I'll click the release button and get the related Cassandra PRs rebased and 
>> ready for commits.
>> Doug
>>> On Oct 15, 2025, at 9:59 AM, Doug Rohrer  wrote:
>>> 
>>> Fair enough - I seem to run into this issue every time I end up doing a 
>>> vote, because, of course, 72 hours makes it easy to bleed into a weekend. 
>>> I'll just generally consider non-work days not part of the vote and just 
>>> wait long enough to allow folks to check, but to your point, calling out a 
>>> specific time isn't great either... I suppose we could say "The vote will 
>>> be open for a minimum of 72 hours" in this case, which would both cover the 
>>> requirement and allow some wiggle room.
>>> 
 On Oct 14, 2025, at 2:34 PM, Brandon Williams  wrote:
 
 I think 72 hours meets the minimum requirement, and beyond that the
 Release Manager has discretion.   I don't think calling out when the
 vote ends is a great idea because you often need to let the votes run
 longer in order to garner enough votes to pass, and you won't know you
 need to do that until you get there.
 
 Kind Regards,
 Brandon
 
 On Tue, Oct 14, 2025 at 1:29 PM Josh McKenzie  wrote:
> 
> Out of curiosity, do we happen to have a policy (or opinion) around 
> calling a vote over a weekend? Should we?  Technically, I think "72 
> hours" ended on Sunday afternoon, but seems wrong to assume folks have 
> had a chance to look at email and validate a build over a weekend.
> 
> I was thinking the same thing re: the gocql vote. We should probably just 
> call out something like "vote ends at time X" if it runs over a weekend 
> or something?
> 
> On Tue, Oct 14, 2025, at 12:02 PM, Jeremiah Jordan wrote:
> 
> +1
> 
> On Oct 14, 2025 at 10:49:35 AM, Michael Shuler  
> wrote:
> 
> +1 thanks!
> 
> On 10/7/25 15:56, Doug Rohrer 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  
> 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/  
> 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  
> 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
> 
> 
> 
>>> 
> 

Re: [VOTE] Release dtest-api 0.0.18

[Michael Shuler]

Also, thanks for the nudge - that triggered my attention. "At least 72 
hours" is the way. The number of sub-projects means less concentrated 
attention, so do call it out if you need eyeballs and votes to get to 
the goal.


Kind regards,
Michael

On 10/15/25 08:25, Doug Rohrer wrote:

Thanks to everyone for validating the release - the vote passes with 5 Binding 
and 4 non-binding +1s.

I'll click the release button and get the related Cassandra PRs rebased and 
ready for commits.

Doug


On Oct 15, 2025, at 9:59 AM, Doug Rohrer  wrote:

Fair enough - I seem to run into this issue every time I end up doing a vote, because, of 
course, 72 hours makes it easy to bleed into a weekend. I'll just generally consider 
non-work days not part of the vote and just wait long enough to allow folks to check, but 
to your point, calling out a specific time isn't great either... I suppose we could say 
"The vote will be open for a minimum of 72 hours" in this case, which would 
both cover the requirement and allow some wiggle room.


On Oct 14, 2025, at 2:34 PM, Brandon Williams  wrote:

I think 72 hours meets the minimum requirement, and beyond that the
Release Manager has discretion.   I don't think calling out when the
vote ends is a great idea because you often need to let the votes run
longer in order to garner enough votes to pass, and you won't know you
need to do that until you get there.

Kind Regards,
Brandon

On Tue, Oct 14, 2025 at 1:29 PM Josh McKenzie  wrote:


Out of curiosity, do we happen to have a policy (or opinion) around calling a vote over a 
weekend? Should we?  Technically, I think "72 hours" ended on Sunday afternoon, 
but seems wrong to assume folks have had a chance to look at email and validate a build 
over a weekend.

I was thinking the same thing re: the gocql vote. We should probably just call out 
something like "vote ends at time X" if it runs over a weekend or something?

On Tue, Oct 14, 2025, at 12:02 PM, Jeremiah Jordan wrote:

+1

On Oct 14, 2025 at 10:49:35 AM, Michael Shuler  wrote:

+1 thanks!

On 10/7/25 15:56, Doug Rohrer 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

Re: [VOTE] Release dtest-api 0.0.18

[Francisco Guerrero]

+1 thanks for driving this release!

On 2025/10/10 18:46:45 Yifan Cai wrote:
> +1 (nb)
> 
> Thanks for providing the validate script. I was able to run the script
> after some minor modifications.
> 
> - Yifan
> 
> On Thu, Oct 9, 2025 at 3:09 PM Doug Rohrer  wrote:
> 
> > Ok - let's try this again:
> >
> > Candidate SHA:
> >
> > https://github.com/apache/cassandra-in-jvm-dtest-api/commit/775bfd5283ec77960713e3de2abeb4d068199ef7
> >
> > Tagged 0.0.18
> >
> > Artifacts:
> >
> > https://repository.apache.org/content/repositories/orgapachecassandra-1420/org/apache/cassandra/dtest-api/0.0.18
> >
> > Key signature (this is my RSA key, in KEYS file):
> > 9A648E3DEDA36EE374C4277B602ED2C52277
> >
> > See changes/info below.
> >
> > Attached is a script that will pull down all of the artifacts, verify the
> > GPG signatures, and validate the md5/sha1 files match.
> > NOTE: it'll create a `tmp` directory wherever you run it, so I'd recommend
> > running it in an empty directory somewhere, or just use the text and run
> > the commands manually wherever).
> >
> >
> > Script based very loosely on
> > https://github.com/apache/cassandra-builds/pull/32/files - but since
> > we're not building RPMs/Debian packages it's just to do the validation.
> >
> >
> > New 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.
> >
> >
> > Thanks,
> >
> > Doug
> >
> > On Oct 9, 2025, at 5:52 PM, Doug Rohrer  wrote:
> >
> > 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  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
> >
> >
> >
> >
> 

Re: [VOTE] Release dtest-api 0.0.18

[Doug Rohrer]

Thanks to everyone for validating the release - the vote passes with 5 Binding 
and 4 non-binding +1s.

I'll click the release button and get the related Cassandra PRs rebased and 
ready for commits.

Doug

> On Oct 15, 2025, at 9:59 AM, Doug Rohrer  wrote:
> 
> Fair enough - I seem to run into this issue every time I end up doing a vote, 
> because, of course, 72 hours makes it easy to bleed into a weekend. I'll just 
> generally consider non-work days not part of the vote and just wait long 
> enough to allow folks to check, but to your point, calling out a specific 
> time isn't great either... I suppose we could say "The vote will be open for 
> a minimum of 72 hours" in this case, which would both cover the requirement 
> and allow some wiggle room.
> 
>> On Oct 14, 2025, at 2:34 PM, Brandon Williams  wrote:
>> 
>> I think 72 hours meets the minimum requirement, and beyond that the
>> Release Manager has discretion.   I don't think calling out when the
>> vote ends is a great idea because you often need to let the votes run
>> longer in order to garner enough votes to pass, and you won't know you
>> need to do that until you get there.
>> 
>> Kind Regards,
>> Brandon
>> 
>> On Tue, Oct 14, 2025 at 1:29 PM Josh McKenzie  wrote:
>>> 
>>> Out of curiosity, do we happen to have a policy (or opinion) around calling 
>>> a vote over a weekend? Should we?  Technically, I think "72 hours" ended on 
>>> Sunday afternoon, but seems wrong to assume folks have had a chance to look 
>>> at email and validate a build over a weekend.
>>> 
>>> I was thinking the same thing re: the gocql vote. We should probably just 
>>> call out something like "vote ends at time X" if it runs over a weekend or 
>>> something?
>>> 
>>> On Tue, Oct 14, 2025, at 12:02 PM, Jeremiah Jordan wrote:
>>> 
>>> +1
>>> 
>>> On Oct 14, 2025 at 10:49:35 AM, Michael Shuler  
>>> wrote:
>>> 
>>> +1 thanks!
>>> 
>>> On 10/7/25 15:56, Doug Rohrer 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 >> 
>>> 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/ >> 
>>> 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 >> 
>>> 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
>>> 
>>> 
>>> 
> 

Re: [VOTE] Release dtest-api 0.0.18

[Štefan Miklošovič]

I do not personally count weekends in. I am also trying to be sensible
with timezones. If the majority of people live in the US west / east
coast I will give them extra time to respond etc.

On Wed, Oct 15, 2025 at 5:28 PM Mick  wrote:
>
> i usually give the minimum timeframe an extra 24 hours when it goes over a 
> weekend.
>
> as others have said, it's the timeframe for objections (vetoes) to be raised. 
>  otherwise, beyond the window, we just wait til we've got enough votes.
>
> people are also free to ask for a hold/extension on the timeframe, if they 
> suspect a objection/veto but need time to verify and describe it.
>
>
> > On 14 Oct 2025, at 20:34, Brandon Williams  wrote:
> >
> > I think 72 hours meets the minimum requirement, and beyond that the
> > Release Manager has discretion.   I don't think calling out when the
> > vote ends is a great idea because you often need to let the votes run
> > longer in order to garner enough votes to pass, and you won't know you
> > need to do that until you get there.
> >
> > Kind Regards,
> > Brandon
> >
> > On Tue, Oct 14, 2025 at 1:29 PM Josh McKenzie  wrote:
> >>
> >> Out of curiosity, do we happen to have a policy (or opinion) around 
> >> calling a vote over a weekend? Should we?  Technically, I think "72 hours" 
> >> ended on Sunday afternoon, but seems wrong to assume folks have had a 
> >> chance to look at email and validate a build over a weekend.
> >>
> >> I was thinking the same thing re: the gocql vote. We should probably just 
> >> call out something like "vote ends at time X" if it runs over a weekend or 
> >> something?
> >>
> >> On Tue, Oct 14, 2025, at 12:02 PM, Jeremiah Jordan wrote:
> >>
> >> +1
> >>
> >> On Oct 14, 2025 at 10:49:35 AM, Michael Shuler  
> >> wrote:
> >>
> >> +1 thanks!
> >>
> >> On 10/7/25 15:56, Doug Rohrer 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  >>
> >> 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/  >>
> >> 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  >>
> >> 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
> >>
> >>
> >>
>

Re: [VOTE] Release dtest-api 0.0.18

[Doug Rohrer]

Fair enough - I seem to run into this issue every time I end up doing a vote, 
because, of course, 72 hours makes it easy to bleed into a weekend. I'll just 
generally consider non-work days not part of the vote and just wait long enough 
to allow folks to check, but to your point, calling out a specific time isn't 
great either... I suppose we could say "The vote will be open for a minimum of 
72 hours" in this case, which would both cover the requirement and allow some 
wiggle room.

> On Oct 14, 2025, at 2:34 PM, Brandon Williams  wrote:
> 
> I think 72 hours meets the minimum requirement, and beyond that the
> Release Manager has discretion.   I don't think calling out when the
> vote ends is a great idea because you often need to let the votes run
> longer in order to garner enough votes to pass, and you won't know you
> need to do that until you get there.
> 
> Kind Regards,
> Brandon
> 
> On Tue, Oct 14, 2025 at 1:29 PM Josh McKenzie  wrote:
>> 
>> Out of curiosity, do we happen to have a policy (or opinion) around calling 
>> a vote over a weekend? Should we?  Technically, I think "72 hours" ended on 
>> Sunday afternoon, but seems wrong to assume folks have had a chance to look 
>> at email and validate a build over a weekend.
>> 
>> I was thinking the same thing re: the gocql vote. We should probably just 
>> call out something like "vote ends at time X" if it runs over a weekend or 
>> something?
>> 
>> On Tue, Oct 14, 2025, at 12:02 PM, Jeremiah Jordan wrote:
>> 
>> +1
>> 
>> On Oct 14, 2025 at 10:49:35 AM, Michael Shuler  
>> wrote:
>> 
>> +1 thanks!
>> 
>> On 10/7/25 15:56, Doug Rohrer 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 > 
>> 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/ > 
>> 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 > 
>> 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
>> 
>> 
>> 

Re: [VOTE] Release dtest-api 0.0.18

[Josh McKenzie]

+1

Attaching an updated validation script; maybe we should have a central repo 
w/the scripts to validate our various releases...

On Fri, Oct 10, 2025, at 3:12 PM, Francisco Guerrero wrote:
> +1 thanks for driving this release!
> 
> On 2025/10/10 18:46:45 Yifan Cai wrote:
> > +1 (nb)
> > 
> > Thanks for providing the validate script. I was able to run the script
> > after some minor modifications.
> > 
> > - Yifan
> > 
> > On Thu, Oct 9, 2025 at 3:09 PM Doug Rohrer  wrote:
> > 
> > > Ok - let's try this again:
> > >
> > > Candidate SHA:
> > >
> > > https://github.com/apache/cassandra-in-jvm-dtest-api/commit/775bfd5283ec77960713e3de2abeb4d068199ef7
> > >
> > > Tagged 0.0.18
> > >
> > > Artifacts:
> > >
> > > https://repository.apache.org/content/repositories/orgapachecassandra-1420/org/apache/cassandra/dtest-api/0.0.18
> > >
> > > Key signature (this is my RSA key, in KEYS file):
> > > 9A648E3DEDA36EE374C4277B602ED2C52277
> > >
> > > See changes/info below.
> > >
> > > Attached is a script that will pull down all of the artifacts, verify the
> > > GPG signatures, and validate the md5/sha1 files match.
> > > NOTE: it'll create a `tmp` directory wherever you run it, so I'd recommend
> > > running it in an empty directory somewhere, or just use the text and run
> > > the commands manually wherever).
> > >
> > >
> > > Script based very loosely on
> > > https://github.com/apache/cassandra-builds/pull/32/files - but since
> > > we're not building RPMs/Debian packages it's just to do the validation.
> > >
> > >
> > > New 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.
> > >
> > >
> > > Thanks,
> > >
> > > Doug
> > >
> > > On Oct 9, 2025, at 5:52 PM, Doug Rohrer  wrote:
> > >
> > > 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  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
> > >
> > >
> > >
> > >
> > 
> 
#!/bin/bash

show_help() {
cat << EOF
Usage: $(basename "$0")   [staging-repo-id]

Validates Apache Cassandra dtest-api release artifacts by verifying GPG 
signatures,
SHA1 and MD5 checksums.

ARGUMENTS:
release-typeType of release to validate (required)
Valid values: 'staged' or 'released'

versionRelease version number to validate (required)
   Example: 0.0.18

staging-repo-idMaven staging repository ID (required only for 'staged')
   This is the numeric ID found in the staging repo URL from
   the vote email (e.g., 1419)
   Extract from URL: In 
https://repository.apache.org/content/repositories/orgapachecassandra-1420/...
   the staging repo ID is 1420
   Must NOT be provided when release-type is 'released

Re: [VOTE] Release dtest-api 0.0.18

[Doug Rohrer]

Thanks Brandon.

I'll leave the vote open until tomorrow afternoon so we have 72 "work hours" of 
vote.

Out of curiosity, do we happen to have a policy (or opinion) around calling a 
vote over a weekend? Should we?  Technically, I think "72 hours" ended on 
Sunday afternoon, but seems wrong to assume folks have had a chance to look at 
email and validate a build over a weekend.

Thanks,

Doug

> On Oct 13, 2025, at 4:35 PM, Brandon Williams  wrote:
> 
> +1
> 
> Kind Regards,
> Brandon
> 
> On Thu, Oct 9, 2025 at 5:09 PM Doug Rohrer  wrote:
>> 
>> Ok - let's try this again:
>> 
>> Candidate SHA:
>> https://github.com/apache/cassandra-in-jvm-dtest-api/commit/775bfd5283ec77960713e3de2abeb4d068199ef7
>> 
>> Tagged 0.0.18
>> 
>> Artifacts:
>> https://repository.apache.org/content/repositories/orgapachecassandra-1420/org/apache/cassandra/dtest-api/0.0.18
>> 
>> Key signature (this is my RSA key, in KEYS file):
>> 9A648E3DEDA36EE374C4277B602ED2C52277
>> 
>> See changes/info below.
>> 
>> Attached is a script that will pull down all of the artifacts, verify the 
>> GPG signatures, and validate the md5/sha1 files match.
>> NOTE: it'll create a `tmp` directory wherever you run it, so I'd recommend 
>> running it in an empty directory somewhere, or just use the text and run the 
>> commands manually wherever).
>> 
>> 
>> Script based very loosely on 
>> https://github.com/apache/cassandra-builds/pull/32/files - but since we're 
>> not building RPMs/Debian packages it's just to do the validation.
>> 
>> 
>> New 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.
>> 
>> 
>> Thanks,
>> 
>> Doug
>> 
>> On Oct 9, 2025, at 5:52 PM, Doug Rohrer  wrote:
>> 
>> 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  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
>> 
>> 
>> 

Re: [VOTE] Release dtest-api 0.0.18

[Doug Rohrer]

Ok - let's try this again:Candidate SHA: https://github.com/apache/cassandra-in-jvm-dtest-api/commit/775bfd5283ec77960713e3de2abeb4d068199ef7Tagged 0.0.18Artifacts:https://repository.apache.org/content/repositories/orgapachecassandra-1420/org/apache/cassandra/dtest-api/0.0.18Key signature (this is my RSA key, in KEYS file):9A648E3DEDA36EE374C4277B602ED2C52277See changes/info below.Attached is a script that will pull down all of the artifacts, verify the GPG signatures, and validate the md5/sha1 files match.NOTE: it'll create a `tmp` directory wherever you run it, so I'd recommend running it in an empty directory somewhere, or just use the text and run the commands manually wherever).#!/bin/bash

# Parameters
# $1 staged|released
# $2 release
# $3 maven artefacts staging repo id (as specified in the repo url found in the 
vote email) (ignored for 'released')
#
# Example use: `./validate.sh staged 0.0.18 1419`  
#
# This script is very basic and experimental. I beg of you to help improve it.
#

###
# prerequisites

# set -x

command -v wget >/dev/null 2>&1 || { echo >&2 "wget needs to be installed"; 
exit 1; }
command -v gpg >/dev/null 2>&1 || { echo >&2 "gpg needs to be installed"; exit 
1; }
command -v sha1sum >/dev/null 2>&1 || { echo >&2 "sha1sum needs to be 
installed"; exit 1; }

( [ "staged" = $1 ] || [ "released" = $1 ] ) || { echo >&2 "first argument must 
be staged or released"; exit 1; }
( [ $# -ge 2 ] ) || { echo >&2 "minimum two arguments must be provided"; exit 
1; }
if [ -z "$3" ] ; then
[ "released" == $1 ] || { echo >&2 "third argument must not be specified 
when first is released"; exit 1; }

maven_repo_url="https://repository.apache.org/content/repositories/releases/org/apache/cassandra/dtest-api/$2";
else
[ "staged" == $1 ] || { echo >&2 "third argument must be specified when 
first is staged"; exit 1; }

maven_repo_url="https://repository.apache.org/content/repositories/orgapachecassandra-$3/org/apache/cassandra/dtest-api/$2";
fi
(curl --output /dev/null --silent --head --fail "${maven_repo_url}") || { echo 
>&2 "Not found: ${maven_repo_url}"; exit 1; }

###

mkdir -p ./tmp/$2
cd ./tmp/$2

# If you want to pull down the complete list of KEYS
# echo "Downloading KEYS"
# wget -q https://downloads.apache.org/cassandra/KEYS
gpg --import KEYS

echo "Downloading ${maven_repo_url}"
wget -Nqnd -e robots=off --recursive --no-parent ${maven_repo_url}

echo
echo "== CHECK RESULTS =="
echo

(compgen -G "*.asc" >/dev/null) || { echo >&2 "No *.asc files found in $(pwd)"; 
exit 1; }
for f in *.asc ; do gpg --verify $f ; done
(compgen -G "*.pom" >/dev/null) || { echo >&2 "No *.pom files found in $(pwd)"; 
exit 1; }
(compgen -G "*.jar" >/dev/null) || { echo >&2 "No *.jar files found in $(pwd)"; 
exit 1; }
for f in *.pom *.jar  ; do echo -n "sha1: " ; echo "$(cat $f.sha1) $f" | 
sha1sum -c - ; echo -n "md5: " ; echo "$(cat $f.md5) $f" | md5sum -c - ; done

echo "Done."
Script based very loosely on https://github.com/apache/cassandra-builds/pull/32/files - but since we're not building RPMs/Debian packages it's just to do the validation.New 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.Thanks,DougOn Oct 9, 2025, at 5:52 PM, Doug Rohrer  wrote: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,DougOn Oct 7, 2025, at 5:56 PM, Doug Rohrer  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.gitCandidate SHA:https://github.com/apache/cassandra-in-jvm-dtest-api/commit/421fe11b8fd862d82f89607c1ae2807657ba6578Tagged with 0.0.18Artifacts:https://repository.apache.org/content/repositories/orgapachecassandra-1419/org/apache/cassandra/dtest-api/0.0.18/Key signature: 2C94EBA59C0BA7E0EDAAE142BF79EF32B05FB5CAChanges since last release:* CASSANDRA-20884 - Move JMX classes to the in-jvm-dtest API projectI 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 vo

Re: [VOTE] Release dtest-api 0.0.18

[Bernardo Botella]

+1Thanks Doug for this APIs release!BernardoEl oct 10, 2025, a las 2:29 p. m., Josh McKenzie  escribió:+1Attaching an updated validation script; maybe we should have a central repo w/the scripts to validate our various releases...On Fri, Oct 10, 2025, at 3:12 PM, Francisco Guerrero wrote:+1 thanks for driving this release!On 2025/10/10 18:46:45 Yifan Cai wrote:> +1 (nb)> > Thanks for providing the validate script. I was able to run the script> after some minor modifications.> > - Yifan> > On Thu, Oct 9, 2025 at 3:09 PM Doug Rohrer  wrote:> > > Ok - let's try this again:> >> > Candidate SHA:> >> > https://github.com/apache/cassandra-in-jvm-dtest-api/commit/775bfd5283ec77960713e3de2abeb4d068199ef7> >> > Tagged 0.0.18> >> > Artifacts:> >> > https://repository.apache.org/content/repositories/orgapachecassandra-1420/org/apache/cassandra/dtest-api/0.0.18> >> > Key signature (this is my RSA key, in KEYS file):> > 9A648E3DEDA36EE374C4277B602ED2C52277> >> > See changes/info below.> >> > Attached is a script that will pull down all of the artifacts, verify the> > GPG signatures, and validate the md5/sha1 files match.> > NOTE: it'll create a `tmp` directory wherever you run it, so I'd recommend> > running it in an empty directory somewhere, or just use the text and run> > the commands manually wherever).> >> >> > Script based very loosely on> > https://github.com/apache/cassandra-builds/pull/32/files - but since> > we're not building RPMs/Debian packages it's just to do the validation.> >> >> > New 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.> >> >> > Thanks,> >> > Doug> >> > On Oct 9, 2025, at 5:52 PM, Doug Rohrer  wrote:> >> > 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  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> >> >> >> >> 

Re: [VOTE] Release dtest-api 0.0.18

[Doug Rohrer]

Is there one more PMC member who could take a few minutes to validate the 
release please? I need one more PMC member to +1.

Thanks,

Doug

> On Oct 11, 2025, at 1:11 PM, Dinesh Joshi  wrote:
> 
> +1
> 
> thank you for providing the validation script. It made validating easy.
> 
> On Sat, Oct 11, 2025 at 8:54 AM Bernardo Botella 
> mailto:conta...@bernardobotella.com>> wrote:
>> +1
>> 
>> Thanks Doug for this APIs release!
>> Bernardo
>> 
>>> El oct 10, 2025, a las 2:29 p. m., Josh McKenzie >> > escribió:
>>> 
>>> 
>>> +1
>>> 
>>> Attaching an updated validation script; maybe we should have a central repo 
>>> w/the scripts to validate our various releases...
>>> 
>>> On Fri, Oct 10, 2025, at 3:12 PM, Francisco Guerrero wrote:
 +1 thanks for driving this release!
 
 On 2025/10/10 18:46:45 Yifan Cai wrote:
 > +1 (nb)
 > 
 > Thanks for providing the validate script. I was able to run the script
 > after some minor modifications.
 > 
 > - Yifan
 > 
 > On Thu, Oct 9, 2025 at 3:09 PM Doug Rohrer >>> > > wrote:
 > 
 > > Ok - let's try this again:
 > >
 > > Candidate SHA:
 > >
 > > https://github.com/apache/cassandra-in-jvm-dtest-api/commit/775bfd5283ec77960713e3de2abeb4d068199ef7
 > >
 > > Tagged 0.0.18
 > >
 > > Artifacts:
 > >
 > > https://repository.apache.org/content/repositories/orgapachecassandra-1420/org/apache/cassandra/dtest-api/0.0.18
 > >
 > > Key signature (this is my RSA key, in KEYS file):
 > > 9A648E3DEDA36EE374C4277B602ED2C52277
 > >
 > > See changes/info below.
 > >
 > > Attached is a script that will pull down all of the artifacts, verify 
 > > the
 > > GPG signatures, and validate the md5/sha1 files match.
 > > NOTE: it'll create a `tmp` directory wherever you run it, so I'd 
 > > recommend
 > > running it in an empty directory somewhere, or just use the text and 
 > > run
 > > the commands manually wherever).
 > >
 > >
 > > Script based very loosely on
 > > https://github.com/apache/cassandra-builds/pull/32/files - but since
 > > we're not building RPMs/Debian packages it's just to do the validation.
 > >
 > >
 > > New 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.
 > >
 > >
 > > Thanks,
 > >
 > > Doug
 > >
 > > On Oct 9, 2025, at 5:52 PM, Doug Rohrer >>> > > > wrote:
 > >
 > > 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 >>> > > > 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 

Re: [VOTE] Release dtest-api 0.0.18

[Josh McKenzie]

> The vote will be open for a minimum of 72 hours
This makes sense to me.

On Wed, Oct 15, 2025, at 9:59 AM, Doug Rohrer wrote:
> Fair enough - I seem to run into this issue every time I end up doing a vote, 
> because, of course, 72 hours makes it easy to bleed into a weekend. I'll just 
> generally consider non-work days not part of the vote and just wait long 
> enough to allow folks to check, but to your point, calling out a specific 
> time isn't great either... I suppose we could say "The vote will be open for 
> a minimum of 72 hours" in this case, which would both cover the requirement 
> and allow some wiggle room.
> 
> > On Oct 14, 2025, at 2:34 PM, Brandon Williams  wrote:
> > 
> > I think 72 hours meets the minimum requirement, and beyond that the
> > Release Manager has discretion.   I don't think calling out when the
> > vote ends is a great idea because you often need to let the votes run
> > longer in order to garner enough votes to pass, and you won't know you
> > need to do that until you get there.
> > 
> > Kind Regards,
> > Brandon
> > 
> > On Tue, Oct 14, 2025 at 1:29 PM Josh McKenzie  wrote:
> >> 
> >> Out of curiosity, do we happen to have a policy (or opinion) around 
> >> calling a vote over a weekend? Should we?  Technically, I think "72 hours" 
> >> ended on Sunday afternoon, but seems wrong to assume folks have had a 
> >> chance to look at email and validate a build over a weekend.
> >> 
> >> I was thinking the same thing re: the gocql vote. We should probably just 
> >> call out something like "vote ends at time X" if it runs over a weekend or 
> >> something?
> >> 
> >> On Tue, Oct 14, 2025, at 12:02 PM, Jeremiah Jordan wrote:
> >> 
> >> +1
> >> 
> >> On Oct 14, 2025 at 10:49:35 AM, Michael Shuler  
> >> wrote:
> >> 
> >> +1 thanks!
> >> 
> >> On 10/7/25 15:56, Doug Rohrer 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  >> 
> >> 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/  >> 
> >> 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  >> 
> >> 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
> >> 
> >> 
> >> 
> 
> 

Re: [VOTE] Release dtest-api 0.0.18

[Mick]

i usually give the minimum timeframe an extra 24 hours when it goes over a 
weekend.

as others have said, it's the timeframe for objections (vetoes) to be raised.  
otherwise, beyond the window, we just wait til we've got enough votes.

people are also free to ask for a hold/extension on the timeframe, if they 
suspect a objection/veto but need time to verify and describe it. 


> On 14 Oct 2025, at 20:34, Brandon Williams  wrote:
> 
> I think 72 hours meets the minimum requirement, and beyond that the
> Release Manager has discretion.   I don't think calling out when the
> vote ends is a great idea because you often need to let the votes run
> longer in order to garner enough votes to pass, and you won't know you
> need to do that until you get there.
> 
> Kind Regards,
> Brandon
> 
> On Tue, Oct 14, 2025 at 1:29 PM Josh McKenzie  wrote:
>> 
>> Out of curiosity, do we happen to have a policy (or opinion) around calling 
>> a vote over a weekend? Should we?  Technically, I think "72 hours" ended on 
>> Sunday afternoon, but seems wrong to assume folks have had a chance to look 
>> at email and validate a build over a weekend.
>> 
>> I was thinking the same thing re: the gocql vote. We should probably just 
>> call out something like "vote ends at time X" if it runs over a weekend or 
>> something?
>> 
>> On Tue, Oct 14, 2025, at 12:02 PM, Jeremiah Jordan wrote:
>> 
>> +1
>> 
>> On Oct 14, 2025 at 10:49:35 AM, Michael Shuler  
>> wrote:
>> 
>> +1 thanks!
>> 
>> On 10/7/25 15:56, Doug Rohrer 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 > 
>> 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/ > 
>> 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 > 
>> 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
>> 
>> 
>> 

Re: [VOTE] Release dtest-api 0.0.18

[Brandon Williams]

I think 72 hours meets the minimum requirement, and beyond that the
Release Manager has discretion.   I don't think calling out when the
vote ends is a great idea because you often need to let the votes run
longer in order to garner enough votes to pass, and you won't know you
need to do that until you get there.

Kind Regards,
Brandon

On Tue, Oct 14, 2025 at 1:29 PM Josh McKenzie  wrote:
>
> Out of curiosity, do we happen to have a policy (or opinion) around calling a 
> vote over a weekend? Should we?  Technically, I think "72 hours" ended on 
> Sunday afternoon, but seems wrong to assume folks have had a chance to look 
> at email and validate a build over a weekend.
>
> I was thinking the same thing re: the gocql vote. We should probably just 
> call out something like "vote ends at time X" if it runs over a weekend or 
> something?
>
> On Tue, Oct 14, 2025, at 12:02 PM, Jeremiah Jordan wrote:
>
> +1
>
> On Oct 14, 2025 at 10:49:35 AM, Michael Shuler  wrote:
>
> +1 thanks!
>
> On 10/7/25 15:56, Doug Rohrer 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 
> 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/ 
> 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 
> 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
>
>
>

Re: [VOTE] Release dtest-api 0.0.18

[Josh McKenzie]

> Out of curiosity, do we happen to have a policy (or opinion) around calling a 
> vote over a weekend? Should we?  Technically, I think "72 hours" ended on 
> Sunday afternoon, but seems wrong to assume folks have had a chance to look 
> at email and validate a build over a weekend.
I was thinking the same thing re: the gocql vote. We should probably just call 
out something like "vote ends at time X" if it runs over a weekend or something?

On Tue, Oct 14, 2025, at 12:02 PM, Jeremiah Jordan wrote:
> +1
> 
> On Oct 14, 2025 at 10:49:35 AM, Michael Shuler  wrote:
>> +1 thanks!
>> 
>> On 10/7/25 15:56, Doug Rohrer wrote:
>>> Hey folks,
>>> I'd like to propose a new release of the dtest-api that includes 
>>> someupdates to make it easier for Cassandra maintainers to deal with some 
>>> ofthe jmx support classes, and for external consumers of the dtest api 
>>> touse 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 branchesto 
>>> take advantage of these changes as well, which can be updated to usethis 
>>> release and committed once the vote passes.
>>> The vote will be open for 72 hours. Everyone who has tested the buildlis 
>>> invited to vote. Votes by PMC members are considered binding. A votepasses 
>>> if there are at least three binding +1s.
>>> See https://issues.apache.org/jira/browse/CASSANDRA-20884 
>>>  for branches of 
>>> Cassandrafor testing the dtest-api change (which currently use a snapshot 
>>> buildof this).
>>> Thanks,
>>> Doug Rohrer

Re: [VOTE] Release dtest-api 0.0.18

[Jeremiah Jordan]

 +1

On Oct 14, 2025 at 10:49:35 AM, Michael Shuler 
wrote:

> +1 thanks!
>
> On 10/7/25 15:56, Doug Rohrer 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 
> 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/ 
> 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 
> 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
>
>
>
>

Re: [VOTE] Release dtest-api 0.0.18

[Michael Shuler]

+1 thanks!

On 10/7/25 15:56, Doug Rohrer 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/ 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 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

Re: [VOTE] Release dtest-api 0.0.18

[Brandon Williams]

+1

Kind Regards,
Brandon

On Thu, Oct 9, 2025 at 5:09 PM Doug Rohrer  wrote:
>
> Ok - let's try this again:
>
> Candidate SHA:
> https://github.com/apache/cassandra-in-jvm-dtest-api/commit/775bfd5283ec77960713e3de2abeb4d068199ef7
>
> Tagged 0.0.18
>
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1420/org/apache/cassandra/dtest-api/0.0.18
>
> Key signature (this is my RSA key, in KEYS file):
> 9A648E3DEDA36EE374C4277B602ED2C52277
>
> See changes/info below.
>
> Attached is a script that will pull down all of the artifacts, verify the GPG 
> signatures, and validate the md5/sha1 files match.
> NOTE: it'll create a `tmp` directory wherever you run it, so I'd recommend 
> running it in an empty directory somewhere, or just use the text and run the 
> commands manually wherever).
>
>
> Script based very loosely on 
> https://github.com/apache/cassandra-builds/pull/32/files - but since we're 
> not building RPMs/Debian packages it's just to do the validation.
>
>
> New 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.
>
>
> Thanks,
>
> Doug
>
> On Oct 9, 2025, at 5:52 PM, Doug Rohrer  wrote:
>
> 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  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
>
>
>

Re: [VOTE] Release dtest-api 0.0.18

[Dinesh Joshi]

+1

thank you for providing the validation script. It made validating easy.

On Sat, Oct 11, 2025 at 8:54 AM Bernardo Botella <
conta...@bernardobotella.com> wrote:

> +1
>
> Thanks Doug for this APIs release!
> Bernardo
>
> El oct 10, 2025, a las 2:29 p. m., Josh McKenzie 
> escribió:
>
> 
> +1
>
> Attaching an updated validation script; maybe we should have a central
> repo w/the scripts to validate our various releases...
>
> On Fri, Oct 10, 2025, at 3:12 PM, Francisco Guerrero wrote:
>
> +1 thanks for driving this release!
>
> On 2025/10/10 18:46:45 Yifan Cai wrote:
> > +1 (nb)
> >
> > Thanks for providing the validate script. I was able to run the script
> > after some minor modifications.
> >
> > - Yifan
> >
> > On Thu, Oct 9, 2025 at 3:09 PM Doug Rohrer  wrote:
> >
> > > Ok - let's try this again:
> > >
> > > Candidate SHA:
> > >
> > >
> https://github.com/apache/cassandra-in-jvm-dtest-api/commit/775bfd5283ec77960713e3de2abeb4d068199ef7
> > >
> > > Tagged 0.0.18
> > >
> > > Artifacts:
> > >
> > >
> https://repository.apache.org/content/repositories/orgapachecassandra-1420/org/apache/cassandra/dtest-api/0.0.18
> > >
> > > Key signature (this is my RSA key, in KEYS file):
> > > 9A648E3DEDA36EE374C4277B602ED2C52277
> > >
> > > See changes/info below.
> > >
> > > Attached is a script that will pull down all of the artifacts, verify
> the
> > > GPG signatures, and validate the md5/sha1 files match.
> > > NOTE: it'll create a `tmp` directory wherever you run it, so I'd
> recommend
> > > running it in an empty directory somewhere, or just use the text and
> run
> > > the commands manually wherever).
> > >
> > >
> > > Script based very loosely on
> > > https://github.com/apache/cassandra-builds/pull/32/files - but since
> > > we're not building RPMs/Debian packages it's just to do the validation.
> > >
> > >
> > > New 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.
> > >
> > >
> > > Thanks,
> > >
> > > Doug
> > >
> > > On Oct 9, 2025, at 5:52 PM, Doug Rohrer  wrote:
> > >
> > > 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  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
> > >
> > >
> > >
> > >
> >
>
>
> 
>
>

Re: [VOTE] Release dtest-api 0.0.18

[Yifan Cai]

+1 (nb)

Thanks for providing the validate script. I was able to run the script
after some minor modifications.

- Yifan

On Thu, Oct 9, 2025 at 3:09 PM Doug Rohrer  wrote:

> Ok - let's try this again:
>
> Candidate SHA:
>
> https://github.com/apache/cassandra-in-jvm-dtest-api/commit/775bfd5283ec77960713e3de2abeb4d068199ef7
>
> Tagged 0.0.18
>
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1420/org/apache/cassandra/dtest-api/0.0.18
>
> Key signature (this is my RSA key, in KEYS file):
> 9A648E3DEDA36EE374C4277B602ED2C52277
>
> See changes/info below.
>
> Attached is a script that will pull down all of the artifacts, verify the
> GPG signatures, and validate the md5/sha1 files match.
> NOTE: it'll create a `tmp` directory wherever you run it, so I'd recommend
> running it in an empty directory somewhere, or just use the text and run
> the commands manually wherever).
>
>
> Script based very loosely on
> https://github.com/apache/cassandra-builds/pull/32/files - but since
> we're not building RPMs/Debian packages it's just to do the validation.
>
>
> New 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.
>
>
> Thanks,
>
> Doug
>
> On Oct 9, 2025, at 5:52 PM, Doug Rohrer  wrote:
>
> 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  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
>
>
>
>

Re: [VOTE] Release dtest-api 0.0.18

[Doug Rohrer]

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