It's been >72h since the vote was initiated and the result is:

+1  7  (4 binding)
 0  0
-1  0

This vote has PASSED!  I'll start work on finishing the release
shortly; congratulations to everyone whose work is included and thanks
to all who tested and voted!

Jason

On Mon, Jan 19, 2026 at 2:03 PM Tomás Fernández Löbbe
<[email protected]> wrote:
>
> +1
> SUCCESS! [1:03:42.817767]
>
> On Mon, Jan 19, 2026 at 10:15 AM Pierre Salagnac <[email protected]>
> wrote:
>
> > +1, not binding
> >
> > SUCCESS! [0:47:08.218950]
> >
> >
> >
> > Thanks,
> >
> > Pierre
> >
> >
> >
> > Le dim. 18 janv. 2026 à 21:23, Arrieta, Alejandro <
> > [email protected]> a écrit :
> >
> > > Hello Team,
> > >
> > > +1 non binding.
> > > SUCCESS! [0:41:24.267444]
> > >
> > > Kind Regards,
> > > Alejandro Arrieta
> > >
> > > On Sun, Jan 18, 2026 at 4:54 PM Jan Høydahl <[email protected]>
> > wrote:
> > >
> > > > Hi
> > > >
> > > > I change my vote to +1, leaving it up to you Jason. I think it is more
> > > > important to get a bugfix release out the door than 100% correct
> > > changelog
> > > > in the tarball.
> > > >
> > > > Jan
> > > >
> > > > > 16. jan. 2026 kl. 16:53 skrev Jan Høydahl <[email protected]>:
> > > > >
> > > > > I think it’s a -0
> > > > > We can patch the online changelog.
> > > > >
> > > > > Jan Høydahl
> > > > >
> > > > >> 16. jan. 2026 kl. 16:20 skrev Jason Gerlowski <
> > [email protected]
> > > >:
> > > > >>
> > > > >> Hey all,
> > > > >>
> > > > >> Thanks for pointing out the changelog issues Jan.  Do we think this
> > > > >> merits a re-spin in its own right, or is it a "-0" sort of concern?
> > > > >>
> > > > >> Best,
> > > > >>
> > > > >> Jason
> > > > >>
> > > > >>> On Thu, Jan 15, 2026 at 6:33 PM Jan Høydahl <[email protected]
> > >
> > > > wrote:
> > > > >>>
> > > > >>> I'm afraid there are changelog issues in RC2 as well
> > > > >>>
> > > > >>> - There's a file in changelog/unreleased folder. In a release there
> > > > should never be any
> > > > >>> - The HTML changelog is not re-generated before release
> > > >
> > >
> > https://dist.apache.org/repos/dist/dev/solr/solr-9.10.1-RC2-rev-c135e6335c7158fa26e96b0dc386f825255b47c0/solr/9.10.1/changes/Changes.html#v9.10.1.fixed
> > > > >>> - The 9.10.1 section contains a release date 2026-01-08. That date
> > is
> > > > wrong by a whole lot. we should not use a date at all for the current
> > > > release.
> > > > >>>
> > > > >>> I'm working on some additions to smoke tester in
> > > > https://issues.apache.org/jira/browse/SOLR-18070 to catch things like
> > > > this..
> > > > >>>
> > > > >>> Jan
> > > > >>>
> > > > >>>>> 15. jan. 2026 kl. 17:46 skrev Rich Bowen <[email protected]>:
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> On 2026/01/15 15:43:43 Jason Gerlowski wrote:
> > > > >>>>> Please vote for release candidate 2 for Solr 9.10.1
> > > > >>>>> [ ] +1  approve
> > > > >>>>> [ ] +0  no opinion
> > > > >>>>> [ ] -1  disapprove (and reason why)
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> +1 (non-binding)
> > > > >>>>
> > > > >>>> * Verified signatures and hashes on the following files as per
> > > > https://apache.org/info/verification.html
> > > > >>>> - solr-9.10.1-slim.tgz (SHA512, GPG signature)
> > > > >>>> - solr-9.10.1-src.tgz (SHA512, GPG signature)
> > > > >>>> - solr-9.10.1.tgz (SHA512, GPG signature)
> > > > >>>> * Verified LICENSE and NOTICE files
> > > > >>>>
> > > > >>>> FWIW, the NOTICE files have 2025 dates in them. This is
> > *definitely*
> > > > not a show-stopper, but perhaps something to tweak for next time.
> > > > >>>>
> > > > >>>>
> > > ---------------------------------------------------------------------
> > > > >>>> 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]
> > > >
> > > >
> > >
> >

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

Reply via email to