Hey everyone,

I am officially back and ready to begin the process for 9.2. How are we
doing with regards to blockers right now?

So I see 4 tickets that are tagged to 9.2 in JIRA but not completed. Do we
have updates for these items?

   - SOLR-16653 <https://issues.apache.org/jira/browse/SOLR-16653>
   - SOLR-9168 <https://issues.apache.org/jira/browse/SOLR-9168>
   - SOLR-8803 <https://issues.apache.org/jira/browse/SOLR-8803>
   - SOLR-16681 <https://issues.apache.org/jira/browse/SOLR-16681> (mentioned
   above)

I also see work going on for the Lucene 9.5 upgrade. Do we want to block
9.2 on this upgrade, or do we want to wait for 9.3? I think I am leaning
towards including Lucene 9.5 in Solr 9.2, but if we don't think it's
feasible we can move forward without it.

- Houston

On Wed, Mar 1, 2023 at 3:49 AM Jan Høydahl <jan....@cominvent.com> wrote:

> I’m ok with documenting it as a limitation as a first step + throw a http
> 400 error.
>
> Jan Høydahl
>
> > 1. mar. 2023 kl. 08:21 skrev Mikhail Khludnev <m...@apache.org>:
> >
> > Hello, colleagues!
> > How can we triage https://issues.apache.org/jira/browse/SOLR-16681
> > Replacing uniqueKey field via fl doesn't work since 9.0?
> > I don't have an elegant solution. Will we just declare it as a known
> > bug/limitation?
> >
> >> On Fri, Feb 17, 2023 at 9:07 PM Houston Putman <hous...@apache.org>
> wrote:
> >>
> >> Hey everyone,
> >>
> >> It's been a while since Solr 9.1 was released, and we have a ton of
> great
> >> things to show off in 9.2:
> >>
> >> - Jetty 10
> >> - JAX-RS
> >> - Lucene 9.5
> >>
> >> I volunteer to do the release starting in the week of March 6th, unless
> >> anyone else objects or wants to do it themselves.
> >>
> >> - Houston
> >>
> >
> >
> > --
> > Sincerely yours
> > Mikhail Khludnev
> > https://t.me/MUST_SEARCH
> > A caveat: Cyrillic!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> For additional commands, e-mail: dev-h...@solr.apache.org
>
>

Reply via email to