Hi all,
for previous releases, we had a two-stage freeze: first, feature freeze (no new features, only bugfixes), followed by full freeze for a short time and then a release. This time, I propose that we start even earlier with an even milder freeze: a _refactoring freeze_ which blocks any wide-ranging, deep-going refactorings that are not focused on adding a specific feature or fixing a specific bug.
In particular, this means no lib migrations, no rewriting and rearranging code "for general correctness", and no 2geom syncs "just in case" until the release. I realize this is all done for good reasons, but experience shows that each such wave of changes brings bugs that keep popping up long after the wave has passed.
So, if there are no objections, let's finish and commit any refactorings that are pending, and set a date after which we will only be allowed to commit focused, easily testable features and bugfixes.