Currently there are three tickets that I have added as blockers: (All should be merged by Monday, when I plan to cut an RC)
- SOLR-16675 <https://issues.apache.org/jira/browse/SOLR-16675> - SOLR-16878 <https://issues.apache.org/jira/browse/SOLR-16878> - SOLR-16877 <https://issues.apache.org/jira/browse/SOLR-16877> I also have 1 small PR that I plan to backport as well: https://github.com/apache/solr/pull/1766 Please comment here before backporting to branch_9_3. - Houston On Fri, Jul 7, 2023 at 1:21 PM Houston Putman <hous...@apache.org> wrote: > NOTICE: > > Branch branch_9_3 has been cut and versions updated to 9.4 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 9.3 and priority "Blocker" will delay > a release candidate build. >
