Hey everyone,

Trying to get organized around the release. From my point of view, this is
the state of unfinished work:

Looking at the Solr 9.2 blockers (
https://issues.apache.org/jira/projects/SOLR/versions/12352353), we
currently have two:

   - SOLR-9168 <https://issues.apache.org/jira/browse/SOLR-9168>: It looks
   like this has a patch, that was +1'ed by Kevin, but it hasn't had movement
   since October.
   - SOLR-8803 <https://issues.apache.org/jira/browse/SOLR-8803> (assigned
   to Shawn): This has a good amount of commits, but the comments seem like it
   isn't done yet?
   I think this is the only thing we can't drop from this release, since
   there is already a good amount of work done in the 9.2 line.

Shawn, do you still want to move forward with both of these for the 9.2
release? If so, do you have a timeline?

>From this thread:

   - SOLR-8975, SOLR-10466: Eric, how are these coming along, do you still
   want to get them in for this release?
   - Alessandro, how are your issues coming along, do you think they should
   be merged in.a few days? Also do you have links to the JIRAs?

If this is all wrapped up, I'll start the release tomorrow.

- Houston

On Mon, Mar 13, 2023 at 1:02 PM Houston Putman <hous...@apache.org> wrote:

> Hey everyone,
>
> I'm planning on cutting the branch today, and seeing what our blockers
> look like.
>
> Once again, please ensure the JIRAs that must make it into 9.2 have the
> blocker attribute added.
> Otherwise I'm going to move forward in a few days, unless there are issues
> that we see arise.
>
> - Houston
>
> On Mon, Mar 13, 2023 at 1:06 PM Alessandro Benedetti <a.benede...@sease.io>
> wrote:
>
>> I have some issues my team is working on, and we would potentially love to
>> see them in 9.2 .
>> But I don't want to block anything and I suspect they'll get merged by the
>> end of this week.
>>
>> Any estimation for the branch cut? So we may potentially include them.
>>
>> Cheers
>> --------------------------
>> *Alessandro Benedetti*
>> Director @ Sease Ltd.
>> *Apache Lucene/Solr Committer*
>> *Apache Solr PMC Member*
>>
>> e-mail: a.benede...@sease.io
>>
>>
>> *Sease* - Information Retrieval Applied
>> Consulting | Training | Open Source
>>
>> Website: Sease.io <http://sease.io/>
>> LinkedIn <https://linkedin.com/company/sease-ltd> | Twitter
>> <https://twitter.com/seaseltd> | Youtube
>> <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ> | Github
>> <https://github.com/seaseltd>
>>
>>
>> On Tue, 7 Mar 2023 at 19:08, Houston Putman <hous...@apache.org> wrote:
>>
>> > I'll cut the branch in a few days, so go for it and merge tomorrow.
>> Please
>> > do add 9.2 as the Fix Version so that we can track this correctly.
>> >
>> > - Houston
>> >
>> > On Tue, Mar 7, 2023 at 1:06 PM Andy Webb <andywebb1...@gmail.com>
>> wrote:
>> >
>> > > hi Houston,
>> > >
>> > > I have https://issues.apache.org/jira/browse/SOLR-16643 in progress -
>> > > would
>> > > like that to go into 9.2 if possible, but it's not critical. I'm away
>> so
>> > > won't be in a position to merge that until this time tomorrow at the
>> > > earliest. It'll also be my first commit, and I want to make sure I'm
>> > doing
>> > > it right! I'm intending to join the Meetup to say hi to folk, could
>> chat
>> > > about it then.
>> > >
>> > > thanks,
>> > > Andy
>> > >
>> > >
>> > > On Tue, 7 Mar 2023 at 15:18, Houston Putman <hous...@apache.org>
>> wrote:
>> > >
>> > > > 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