There were lots of Blocker issues with affectsVersion as 9.1. I assume the intention was to have them be available in 9.1? I've changed them to fixVersion = 9.1 (blocker).
On Fri, Oct 7, 2022 at 5:17 PM Christine Poerschke (BLOOMBERG/ LONDON) < cpoersc...@bloomberg.net> wrote: > Thanks! Merging and backporting is now complete. > > From: dev@solr.apache.org At: 10/07/22 04:07:31 UTC+1:00To: Christine > Poerschke (BLOOMBERG/ LONDON ) , dev@solr.apache.org > Subject: Re: New branch and feature freeze for Solr 9.1.0 > > Sure, please go ahead. > > On Fri, 7 Oct, 2022, 12:15 am Christine Poerschke (BLOOMBERG/ LONDON), < > cpoersc...@bloomberg.net> wrote: > > > I'd like to include https://github.com/apache/solr/pull/1051 for > > https://issues.apache.org/jira/browse/SOLR-13219 bug fix please if that > > is okay? > > > > Christine > > > > From: dev@solr.apache.org At: 10/04/22 12:33:03 UTC+1:00To: > > dev@solr.apache.org > > Subject: Re: New branch and feature freeze for Solr 9.1.0 > > > > Sure, please go ahead. > > > > > > I'm concerned about the intermittent test failures. Noble is looking at > it, > > will hold off the release for now. Also, I'm out on vacation for next 3 > > days (Dusshera holidays in India). Will resume the release process once > I'm > > back. > > > > > > On Tue, 4 Oct, 2022, 12:01 am Tomás Fernández Löbbe, < > > tomasflo...@gmail.com> > > wrote: > > > > > I'd like to merge the PR for SOLR-16229 ( > > > https://github.com/apache/solr/pull/1047) to 9.1 branch if that's OK. > > > > > > Tomás > > > > > > On Mon, Sep 26, 2022 at 11:12 PM Ishan Chattopadhyaya < > > > ichattopadhy...@gmail.com> wrote: > > > > > > > NOTICE: > > > > > > > > Branch branch_9_1 has been cut and versions updated to 9.2 on stable > > > > branch. > > > > > > > > Please note the following: > > > > > > > > * No new features may be committed to the branch without discussion > on > > > the > > > > dev-list. > > > > * 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. > > > > * Only Jira issues with Fix version 9.1 and priority "Blocker" will > > delay > > > > a release candidate build. > > > > > > > > > > > > > > > >
