> isn't a patch/minor/major version matter

Hmm.. does this mean that we're ok to release 10.1 soon but with some still 
unpatched security bugs? If that's the case then I volunteer to be the RM for 
10.1 and start the ball rolling.

Andrzej

On 2026/09/02 13:27:22 David Smiley wrote:
> A minor release doesn't have to take long.  The RM (you?) can choose to be
> stringent -- disapproving proposals to add yet another feature.  I actually
> think we're pretty good about that in general.
> 
> The _real_ reason releases have been delayed this year is due to a security
> backlog, which isn't a patch/minor/major version matter.
> 
> On Wed, Sep 2, 2026 at 6:47 AM Andrzej Bialecki <[email protected]> wrote:
> 
> > I'm not against it. My only concern is that the list of outstanding issues
> > for 10x is still very long, and as we all know when the release process
> > starts rolling there's a sudden flurry of activity to include this or that
> > fix / new feature, and the preparation for release may drag on for months.
> >
> > I think that given the serious nature of the bug in SOLR-18414 / 18156 and
> > the CrossDC bugs we should aim for something very much sooner than that,
> > that's why I proposed 10.0.1.
> >
> > Although the difference in failed tests between 10.0.0 and 10x (55 vs 2)
> > reported in SOLR-18414 suggests 10x is already in much better shape than
> > with the fix in SOLR-18156. So if we can agree on just starting the process
> > with whatever is already there (plus/minus a few tickets in flight) then
> > sure, why not, we can do 10.1.
> >
> > Andrzej
> >
> > On 2026/09/02 09:43:47 Eric Pugh wrote:
> > > I think it’s very much time for a 10.1….   We’ve updated so many
> > > dependencies, we’ve found some bugs and fixes for 10, and the effort of a
> > > 10.0.1 and a 10.1 should be similar???
> > >
> > > On Sep 1, 2026, at 9:36 AM, Andrzej Białecki <[email protected]> wrote:
> > >
> > > Hi,
> > >
> > > There have been a few important bugs fixed on branch_10x. IMHO they
> > should
> > > be released ASAP because they either break a major area of existing
> > > functionality (SOLR-18156), may cause request failures (SOLR-18350), or
> > > cause silent data loss in CrossDC (tickets SOLR-18408 … SOLR-18412).
> > >
> > > While 10.1 still seems to be several months away (unless I missed
> > > something?) these issues are critical bugs that exist in the latest
> > > released version 10.0.
> > >
> > > The JoinQuery fix has been done a while ago, as was SOLR-18350. I’m
> > > actively working on the CrossDC issues and should wrap it up within a
> > week
> > > or two.
> > >
> > > I’d like to propose creating a 10.0.1 bug fix release that includes these
> > > (and maybe other?) fixes.
> > >
> > > Andrzej
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > > Disclaimer
> > >
> > > The information contained in this communication from the sender is
> > confidential. It is intended solely for use by the recipient and others
> > authorized to receive it. If you are not the recipient, you are hereby
> > notified that any disclosure, copying, distribution or taking action in
> > relation of the contents of this information is strictly prohibited and may
> > be unlawful.
> > >
> > > This email has been scanned for viruses and malware, and may have been
> > automatically archived by Mimecast, a leader in email security and cyber
> > resilience. Mimecast integrates email defenses with brand protection,
> > security awareness training, web security, compliance and other essential
> > capabilities. Mimecast helps protect large and small organizations from
> > malicious activity, human error and technology failure; and to lead the
> > movement toward building a more resilient world. To find out more, visit
> > our website.
> > >
> >
> > ---------------------------------------------------------------------
> > 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