That's a great idea Josh. I have an informal list of things I had been doing when validating the previous releases which includes:
* Verify repo tag matches the sha in the email. * Configure a gradle project with the nexus staging repo as a repository and pull in the artifacts and run a basic e2e test. * Download the artifacts from subversion, verify keys and checksums, extract artifacts. * Build the source tarball and ensure the unit tests pass. I could probably make some kind parameterized of docker image-based verification process for that. I'll see what others have done for the C* releases and come up with something that we can use to vet the release. We're planning on a 4.19.2 release already so would be nice to use that for this release and further ones as well. Thanks, Andy On Wed, Oct 15, 2025 at 9:29 AM Josh McKenzie <[email protected]> wrote: > In keeping with the recent trends on releases - does anyone have a script > they use to validate releases they could attach to the thread we could then > iterate on to help ease the release validation process? > > On Tue, Oct 14, 2025, at 5:24 PM, Tolbert, Andy wrote: > > Hello all, > > > I’m proposing the test build of Cassandra Java Driver 4.19.1 for release. > > sha1: 77b2baebebfa208e2a7a29f6b09b6cb86e3a4b61 > > Git: https://github.com/apache/cassandra-java-driver/tree/4.19.1 > > Maven Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1423 > > Source and Binary Artifacts: > https://dist.apache.org/repos/dist/dev/cassandra/cassandra-java-driver/4.19.1/ > > > The vote will be open for 72 hours (longer if needed). > > > 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 and no -1's. > > Thanks, > Andy > > >
