SUCCESS! [0:43:59.030883]

There is a changelog file left in unreleased/ folder, and the latest fixes for 
release-date are not present in CHANGELOG.md, i.e. lacks a generate.

Probably the smoke tester should add some checks related to changelog... Butl 
lIkely not enough to stop a release..

+0

Jan

> 9. jan. 2026 kl. 23:09 skrev Jason Gerlowski <[email protected]>:
> 
> Please vote for release candidate 1 for Solr 9.10.1
> 
> The artifacts can be downloaded from:
> https://dist.apache.org/repos/dist/dev/solr/solr-9.10.1-RC1-rev-35230aec19bbbb60d79b78f7be39b868af3170c0
> 
> You can run the smoke tester directly with this command:
> 
> python3 -u dev-tools/scripts/smokeTestRelease.py \
> https://dist.apache.org/repos/dist/dev/solr/solr-9.10.1-RC1-rev-35230aec19bbbb60d79b78f7be39b868af3170c0
> 
> You can build a release-candidate of the official docker images (full
> & slim) using the following command:
> 
> SOLR_DOWNLOAD_SERVER=https://dist.apache.org/repos/dist/dev/solr/solr-9.10.1-RC1-rev-35230aec19bbbb60d79b78f7be39b868af3170c0/solr
> && \
>  docker build $SOLR_DOWNLOAD_SERVER/9.10.1/docker/Dockerfile.official-full \
>    --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
>    -t solr-rc:9.10.1-1 && \
>  docker build $SOLR_DOWNLOAD_SERVER/9.10.1/docker/Dockerfile.official-slim \
>    --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
>    -t solr-rc:9.10.1-1-slim
> 
> The vote will be open for at least 72 hours i.e. until 2026-01-12
> 23:00 UTC. (I'll likely leave the vote open until at least Tuesday or
> Wednesday since I'm starting right before the weekend.)
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Here is my +1
> 
> Best,
> 
> Jason
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to