Hi. Sorry, I should have made that clearer. I am planning the first RC for tomorrow morning.
> Are bug fixes still allowed into the release branch until then? Not really sure, maybe others can chime in? my guess is this can go in if it is a blocker. best, alex On Wed, Oct 4, 2023 at 9:45 AM Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > Can you please suggest when you're planning to spin the first RC? Are bug > fixes still allowed into the release branch until then? > > On Wed, 4 Oct, 2023, 9:58 pm Alex Deparvu, <stilla...@apache.org> wrote: > > > Quick update, we are blocker free. Both issues have been resolved and as > > far as I can see there is no pending issue for 9.4 anymore. > > > > best > > alex > > > > > > On Tue, Oct 3, 2023 at 2:45 PM Walter Underwood <wun...@wunderwood.org> > > wrote: > > > > > I think this is missing a some words: > > > > > > "A new Always-On trace id generator and the rid parameter is being > > > deprecated” > > > > > > Maybe “…generator has been added and…”? As it stands, it looks like the > > > new trace id generator is being deprecated. > > > > > > The circuit breaker descriptions are accurate, but probably do not need > > to > > > be capitalized. In general, there seem to be extra capitalizations, > like > > > “Always-On” and “Backup, Restore, and Split”. > > > > > > wunder > > > Walter Underwood > > > wun...@wunderwood.org > > > http://observer.wunderwood.org/ (my blog) > > > > > > > On Oct 3, 2023, at 2:00 PM, Alex Deparvu <stilla...@apache.org> > wrote: > > > > > > > > Please update the draft release notes if you have any suggestions: > > > > > > > > https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote9_4_0 > > > > > > > > best, > > > > alex > > > > > > > > > > > > > > > > On Tue, Oct 3, 2023 at 11:26 AM Alex Deparvu <stilla...@apache.org> > > > wrote: > > > > > > > >> NOTICE: > > > >> > > > >> Branch branch_9_4 has been cut and versions updated to 9.5 on stable > > the > > > >> 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.4 and priority "Blocker" will > > > delay > > > >> a release candidate build. > > > >> > > > > > > > > >
