Hi Tim, I'm still working on SOLR-15555, the code and benchmarking
both look pretty good, but I've got a few last unit tests that I need
to chase down. Hopefully taken care of by today or tomorrow, I'll be
sure to keep you updated though.


On Thu, Sep 9, 2021 at 11:39 AM Timothy Potter <[email protected]> wrote:
>
> I found https://issues.apache.org/jira/browse/SOLR-15620 while testing
> the schema designer. I haven't built the RC yet, so going to see if I
> can get this in today.
>
> On Tue, Sep 7, 2021 at 12:36 PM Timothy Potter <[email protected]> wrote:
> >
> > NOTICE:
> >
> > Branch branch_8_10 has been cut and versions updated to 8.11 on stable 
> > branch.
> >
> > Please observe the normal rules:
> >
> > * No new features may be committed to the branch.
> >
> > * Documentation patches, build patches and serious bug fixes may be
> >   committed to the branch. However, you should submit all patches you
> >   want to commit to Jira first to give others the chance to review
> >   and possibly vote against the patch. Keep in mind that it is our
> >   main intention to keep the branch as stable as possible.
> >
> > * All patches that are intended for the branch should first be committed
> >   to the unstable branch, merged into the stable branch, and then into
> >   the current release branch.
> >
> > * Normal unstable and stable branch development may continue as usual.
> >   However, if you plan to commit a big change to the unstable branch
> >   while the branch feature freeze is in effect, think twice: can't the
> >   addition wait a couple more days? Merges of bug fixes into the branch
> >   may become more difficult.
> >
> > * Only Jira issues with Fix version 8.10 and priority "Blocker" will delay
> >   a release candidate build.
> > ----
>
> ---------------------------------------------------------------------
> 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