Code Freeze Exception Request Language Collocations
Practise the standard verbs for requesting and logging code freeze exceptions.
0 / 5 completed
1 / 5
Fill in: 'We ___ a code freeze exception request through the release manager, rather than a merge nobody's actually cleared during the freeze.'
We 'submit a request' — the standard, simple collocation for asking to merge code during a freeze window. The other options are less idiomatic here.
2 / 5
Fill in: 'Merging without an approved exception during a freeze can ___ the whole release blocked on a change nobody's actually signed off.'
We say an unapproved merge will 'leave' the release blocked — the standard, natural collocation for the resulting delay. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the business justification in the exception request, rather than a merge nobody's actually explained the urgency of.'
We 'state a justification' — the standard, simple collocation for explaining why a freeze exception is needed. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every exception request against the freeze policy before approving, rather than a merge nobody's actually checked against the rules.'
We 'check a request' — the standard, simple collocation for confirming an exception fits the freeze policy. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ every approved exception in the release log, rather than a merge nobody's actually recorded for the postmortem.'
We 'log an exception' — the standard, simple collocation for recording freeze exceptions for later review. The other options aren't idiomatic here.