New branch and feature freeze for Solr 9.9.0

[Houston Putman <ho...@apache.org>]

NOTICE:

Branch branch_9_9 has been cut and versions updated to 9.10 on the 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 9.9 and priority "Blocker" will delay
  a release candidate build.

Re: New branch and feature freeze for Solr 9.9.0

[Andrzej Białecki <ab...@getopt.org>]

Hi,

I’d like to include SOLR-17804. This has been merged into main and PRs exist for branches 9x and 9_9 (https://github.com/apache/solr/pull/3425).

Although PR-3425 (and PR-3424) are failing automated builds due to OOM during compileJava task… any suggestions?

Andrzej

> On 7 Jul 2025, at 19:50, Houston Putman <ho...@apache.org> wrote:
> 
> NOTICE:
> 
> Branch branch_9_9 has been cut and versions updated to 9.10 on the 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 9.9 and priority "Blocker" will delay
>  a release candidate build.