Practise natural English collocations for planning, scheduling, and managing software releases.
0 / 5 completed
1 / 5
The team agreed to ___ a release every two weeks to keep delivery predictable.
Schedule a release is the standard IT collocation meaning to set a planned date and time for a release. 'Launch' is used when you actually ship, not during planning. 'Open' and 'draft' don't collocate naturally with 'release' in this context.
2 / 5
We need to ___ the release two days early because of a critical security patch.
Cut a release is the conventional software engineering phrase meaning to create and publish a release build. 'Chop', 'trim', and 'slice' are physically similar verbs but are not used with 'release' in IT English.
3 / 5
All feature branches must be merged before we ___ the release.
Freeze a release (or 'code freeze') is the industry-standard term for stopping new feature additions before a release. 'Lock down' is informal and ambiguous, while 'seal' and 'stop' are not used in this collocation.
4 / 5
The project manager reminded the team to ___ a deadline for the beta release.
Set a deadline is the standard collocation in project management. 'Put a deadline' and 'place a deadline' are grammatically possible but not idiomatic. 'Fix on a deadline' is non-standard.
5 / 5
We successfully managed to ___ the Q3 milestone despite losing two engineers mid-sprint.
Hit a milestone is the natural IT collocation meaning to successfully complete a milestone on time. 'Reach a milestone' is also acceptable, but 'reach to' is ungrammatical. 'Strike' and 'achieve up' are not used this way.