> So how about the following plan:
>
> !1510 could perhaps be merged faster than usual for an MR on Review,
> !e.g. on Saturday (it has already been reviewed and the latest
> !update was minor changes, I tried a different approach but it was
> !too complex so I eventually went back to the previous approach).
>
> Apart from this peculiar MR, we try to create optimal conditions for
> branching by refraining from merging non-bugfix changes to master
> for a few countdowns. (I've just put !1650, the \simple thing, on
> Waiting.)
>
> On Saturday or Sunday, we do the 2.23.14 release. We explicitly ask
> users to test it, focusing on these points in particular: large
> scores on Windows, -dcompile-scheme-code, and text marks.
>
> If no major issues are reported, we create the branch later next
> week and open master for development again.
>
> Does that sound reasonable?
If Jonas agrees: +1.
Werner
