+1 (binding) I ran the smoketester, did some real basic tire-kicking of the docker image in the operator, and did backup/restore in a tiny collection.
Jason On Fri, Jan 16, 2026 at 2:33 AM Jan Høydahl <[email protected]> wrote: > > Yea, the respin loop must handle this, not just regenerate but also new files > in unreleased folder and re-generate Changes.html > > Jan Høydahl > > > 16. jan. 2026 kl. 03:26 skrev Jason Gerlowski <[email protected]>: > > > > It seems like one missing piece is that the releaseWizard should > > re-generate CHANGELOG.md each time the RM prepares a new release > > candidate? Looking at the "changelog/" directory tree on branch_10_0 > > at least, all of the individual files look as I'd expect: there's no > > duplication between 9.10.1, etc. The problem seems to be that > > CHANGELOG.md was generated "too early" in the process. > > > > Jason > > > >> On Thu, Jan 15, 2026 at 6:55 PM Anshum Gupta <[email protected]> > >> wrote: > >> > >> Oh no. We need to figure out how to handle parallel releases in this case > >> as 9.10.1 release will most likely happen before 10.0. > >> I'd like to continue running this vote and testing until after the 9.10.1 > >> release, and then if the changelog is the only issue we can fix it, spin > >> another RC and release in 72 hours. > >> > >>> On Thu, Jan 15, 2026 at 3:29 PM Jan Høydahl <[email protected]> wrote: > >>> > >>> First thing I notice is that the generated changelog is wrong, both the > >>> CHANGELOG.md file inside the tarballs and the Changes.html. They both > >>> contain the changes from the not-yet-released 9.10.1, and with a wrong > >>> release date > >>> > >>> [9.10.1] - 2026-01-08 > >>> > >>> So I think that either we release 10.0.0 first, without mentioning 9.10.1 > >>> or we wait until 9.10.1 is out the door before the next 10.0.0 RC. > >>> > >>> Jan > >>> > >>>> 15. jan. 2026 kl. 20:53 skrev Anshum Gupta <[email protected]>: > >>>> > >>>> Hi everyone, > >>>> > >>>> Please vote for Release Candidate 2 for Solr 10.0.0 > >>>> > >>>> The artifacts can be downloaded from: > >>>> > >>> https://dist.apache.org/repos/dist/dev/solr/solr-10.0.0-RC2-rev-4c0f36427e2a5ef0a468252f6c3bd863c956aa0c > >>>> > >>>> 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-10.0.0-RC2-rev-4c0f36427e2a5ef0a468252f6c3bd863c956aa0c > >>>> > >>>> 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-10.0.0-RC2-rev-4c0f36427e2a5ef0a468252f6c3bd863c956aa0c/solr > >>>> && \ > >>>> docker build > >>> $SOLR_DOWNLOAD_SERVER/10.0.0/docker/Dockerfile.official-full > >>>> \ > >>>> --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \ > >>>> -t solr-rc:10.0.0-2 && \ > >>>> docker build > >>> $SOLR_DOWNLOAD_SERVER/10.0.0/docker/Dockerfile.official-slim > >>>> \ > >>>> --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \ > >>>> -t solr-rc:10.0.0-2-slim > >>>> > >>>> > >>>> *The vote will be open for at least 7 days i.e. until 2026-01-22 20:00 > >>> UTC.* > >>>> [ ] +1 approve > >>>> [ ] +0 no opinion > >>>> [ ] -1 disapprove (and reason why) > >>>> > >>>> Here is my +1 > >>>> SUCCESS! [0:53:37.211799] > >>>> > >>>> -- > >>>> Anshum Gupta > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >>> > >> > >> -- > >> Anshum Gupta > > > > --------------------------------------------------------------------- > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
