Thanks for doing a release Houston. There are some bug-fixes we could get in here. For example the JSON enum faceting one, prometheus, and more. I can try to move the ones I was involved with tonight.
Am I right that we needn't change the CHANGES.txt placement on main or branch_9x because, I recall, there's a release step that synchronizes that back up from the release branch? On Mon, Feb 17, 2025 at 4:23 PM Houston Putman <hous...@apache.org> wrote: > NOTICE: > > I am now preparing for a bugfix release from branch branch_9_8 > > Please observe the normal rules for committing to this branch: > > * Before committing to the branch, reply to this thread and argue > why the fix needs backporting and how long it will take. > * All issues accepted for backporting should be marked with 9.8.1 > in JIRA, and issues that should delay the release must be marked as > Blocker > * 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. > * Only Jira issues with Fix version 9.8.1 and priority "Blocker" will delay > a release candidate build. >
