Practise the standard verbs for managing a code freeze window carefully.
0 / 5 completed
1 / 5
Fill in: 'We ___ a code freeze window ahead of the major release, rather than merging risky changes right up to the actual deploy.'
We 'announce a freeze' — the standard, simple collocation for declaring a code freeze period. The other options are less idiomatic here.
2 / 5
Fill in: 'Merging an unreviewed hotfix during the freeze can ___ the release branch destabilized right before it's actually shipped.'
We say an unreviewed merge will 'leave' the branch destabilized — the standard, natural collocation for the resulting risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ freeze exceptions strictly to critical fixes, rather than a loophole every team actually treats as optional.'
We 'limit exceptions' — the standard, simple collocation for restricting what can bypass a code freeze. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every exception request against the release manager's sign-off, rather than merging code nobody's actually approved.'
We 'check a request' — the standard, simple collocation for validating a freeze exception before merging. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the freeze window explicitly on the release calendar, rather than a date range nobody outside the release team actually sees.'
We 'publish a window' — the standard, simple collocation for making a code freeze period visible to everyone. The other options aren't idiomatic here.