Jeremy, the justification for UIFreeze has always been providing a stable target for documentation authors and translators, it is NOT because we believe there will be "inevitable UI issues" that require further freeze-breaking fixes. If the change is justifiable in terms of Feature Freeze, the UIFreeze should not be a barrier here - the change is being proposed in plenty of time for the documentation and translation teams to schedule their work accordingly.
That's not to say this should get a FFe - this is obviously a big change that needs to be carefully considered. But let's please not throw up additional roadblocks that don't follow from our freeze guidelines.
Jeremy, the justification for UIFreeze has always been providing a stable target for documentation authors and translators, it is NOT because we believe there will be "inevitable UI issues" that require further freeze-breaking fixes. If the change is justifiable in terms of Feature Freeze, the UIFreeze should not be a barrier here - the change is being proposed in plenty of time for the documentation and translation teams to schedule their work accordingly.
That's not to say this should get a FFe - this is obviously a big change that needs to be carefully considered. But let's please not throw up additional roadblocks that don't follow from our freeze guidelines.