> The issue I've identified is large changes landing just before the
> freeze. Typically these large changes require subsequent smaller
> changes to make them release-ready, which often requires close design
> involvement.
I don't know the best solution either but the current 3.27/3.28
schedule extends The Freeze by one week (see my other email).
If Design and/or Engagement would like to get head-ups we could either
adjust that wiki page to mention mailing lists, or a team member should
follow release-team@ and forward/discuss relevant changes?
r-t members already sometimes answer "+1 if {docs, translator} team
agrees; I could imagine a similar pattern for design team.
(Or if really needed a formal approval which would require defining
design team members in a position to make decisions.)