> 1. Review and merge the fix this weekend and release 2.23.81, hoping
> that it doesn't break text replacements in other ways. Assuming
> things go well, we could still have the final 2.24.0 in early
> December.
>
> 2. Release 2.23.81 without the fix and instead review it
> properly. Then have a third release candidate 2.23.82 the weekend
> of November 26/27, and delay the final 2.24.0 to mid December
> (maybe the week 12th-18th).
>
> I only had a quick look so far and the fix seems non-trivial to me,
> in particular not a plain revert of a previous commit. It also
> seems to involve GC related problems, which I haven't understood
> yet. I therefore lean towards the second option.
Option 2 is fine with me.
Werner
