As it stands, the vote passes with 7 binding and 3 non-binding +1s. Dinesh pointed out that we usually allow 72 hours for votes (and the Apache Release Policy says that the “SHOULD” last 72 hours), but all previous dtest-api votes I saw were only 24, which is why I left this one at 24 as well.
Given the standard is 72 hours (even though it is a “SHOULD” not a “MUST”), I’m inclined to extend this vote for another 48 hours (which would mean it would close Friday of this week). Any objections? Also, do we have any historical reason why these are only 24 hours vs. 72? Thanks, Doug > On Sep 10, 2024, at 5:16 PM, Doug Rohrer <droh...@apple.com> wrote: > > It was pointed out that auto-correct removed the “d” from “dtest” so just > responding to this with a correct title in case “test-api” wasn’t clear. Vote > will still close at the initial 24-hour period as I don’t think this has > prevented folks from finding and voting so far. > > Doug > >> On Sep 10, 2024, at 1:33 PM, Francisco Guerrero <fran...@apache.org> wrote: >> >> +1 (nb) >> >> On 2024/09/10 14:34:48 Doug Rohrer wrote: >>> Proposing the test build of in-jvm dtest API 0.0.17 for release >>> >>> 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/85b538ca8259dedc2aded8a633cf3174f551f664 >>> Tagged with 0.0.17 >>> >>> Artifacts: >>> https://repository.apache.org/content/repositories/orgapachecassandra-1343/org/apache/cassandra/dtest-api/0.0.17/ >>> >>> Key signature: 9A648E3DEDA36EECCCC374C4277B602ED2C52277 >>> >>> Changes since last release: >>> * CASSANDRA-19783 - In-jvm dtest to detect InstanceClassLoaderLeaks >>> * CASSANDRA-19239 - jvm-dtests crash on java 17 >>> >>> The vote will be open for 24 hours. Everyone who has tested the build >>> is invited to vote. Votes by PMC members are considered binding. A >>> vote passes if there are at least three binding +1s. >
