> We can give another week to cut the RC. That's probably a good idea anyway. Thanks
> There's danger in pushing something big in at the last moment. Fully agree. For me, I just want to get a reasonably contained Tika change in. On Tue, 16 Apr 2024 at 00:19, Gus Heck <gus.h...@gmail.com> wrote: > We can give another week to cut the RC. That's probably a good idea anyway. > But the point of a branch is to allow people to keep working on things they > don't think should go in. There's danger in pushing something big in at the > last moment. For example I might or might not push in SOLR-17151 (I'm on > the fence, feel free to comment in the ticket/PR and talk me in or out of > that), but I've already decided to delay the larger and more risky > SOLR-17158 even though it's fairly close as well. I want it to bake longer. > > We have plenty of content for a release, and of course there's nothing > stopping another release in a month if we have a fresh set of stuff come in > quickly. > > In any case there's been a couple +1's to the original plan so I made the > branch as promised. If there's a consensus to delay we can of course move > it as needed. > > On Mon, Apr 15, 2024 at 10:35 AM Ishan Chattopadhyaya < > ichattopadhy...@gmail.com> wrote: > > > Indeed, quite a few PRs are almost ready. Can we push the feature freeze > by > > a week, please? > > > > On Fri, 12 Apr, 2024, 8:45 pm David Smiley, <dsmi...@apache.org> wrote: > > > > > We do have a lot of PRs that appear to be in an advanced state of > > > readiness. Maybe some have been reviewed by local search teams even > > > albeit not publically here. I'm hoping we could rally around more > > > peer review of these to get the hard work of others merged. I suppose > > > this is an ever-present concern but an impending release reminds me of > > > our PR backlog. For my part, I scanned through a couple pages of PRs; > > > looked at some. > > > > > > On Mon, Apr 8, 2024 at 12:55 PM Gus Heck <gus.h...@gmail.com> wrote: > > > > > > > > It's been about 3 months since we started our last release > discussion, > > > and Jira > > > > shows > > > > < > > > > > > https://issues.apache.org/jira/browse/SOLR-17126?jql=project%20%3D%20SOLR%20AND%20fixVersion%20%3D%209.6.0%20ORDER%20BY%20issuetype%20ASC%2C%20status%20DESC > > > > > > > > that we have: > > > > > > > > 5 bug fixes > > > > 1 feature (query time distributed stats disable) > > > > 11 improvements > > > > 7 sub tasks, several of which represent new features including CPU > > > limited > > > > requests > > > > 3 tasks, including the upgrade to Lucene 9.10 > > > > > > > > Only two are not resolved, but one seems to have commits and the > other > > > had > > > > a PR ready in late Feb... > > > > > > > > It seems like there are quite a few things now that should be made > more > > > > widely available to users. > > > > > > > > I'm happy to volunteer as RM, though it will be my first time so I > may > > > have > > > > questions. I propose that we cut the branch Next Monday April 15 and > > > > prepare the first RC. > > > > > > > > - Gus > > > > > > > > -- > > > > http://www.needhamsoftware.com (work) > > > > https://a.co/d/b2sZLD9 (my fantasy fiction book) > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > > > For additional commands, e-mail: dev-h...@solr.apache.org > > > > > > > > > > > -- > http://www.needhamsoftware.com (work) > https://a.co/d/b2sZLD9 (my fantasy fiction book) >
