Practice the key verb+noun collocations used when coordinating, cutting, tagging, and communicating software releases in English.
0 / 5 completed
1 / 5
Fill in: 'Who is the release manager responsible for ___ this Thursday's release?'
We 'coordinate a release' — 'coordinate' captures the multi-team synchronisation aspect of a release. 'Manage' implies top-down control; 'run' is informal; 'own a release' focuses on accountability, not the act of orchestrating it.
2 / 5
Fill in: 'We will ___ the release branch from main on Tuesday evening.'
We 'cut a release branch' — 'cut' is the git workflow collocation for creating a branch at a specific commit as the starting point for a release. 'Create' is generic; 'make' is informal; 'branch' is a verb but requires additional context ('branch off').
3 / 5
Fill in: 'Once QA signs off, we will ___ v2.4.0 in GitHub and upload the changelog.'
We 'tag a release' — 'tag' is the standard git/GitHub collocation for creating a version marker on a commit. 'Mark' is informal; 'label' is used in issue trackers; 'name a release' refers to giving it a title, not the technical act of tagging.
4 / 5
Fill in: 'We are ready to ___ version 3.0 to production after the final smoke tests pass.'
We 'ship to production' — 'ship' is the engineering collocation that emphasises delivering working software to end users. 'Push to production' refers specifically to the deployment step; 'release to production' is formal; 'launch to production' is a marketing phrase.
5 / 5
Fill in: 'The release manager will ___ the release on the #engineering Slack channel once deployment is complete.'
We 'communicate a release' — 'communicate' is the professional collocation for formally notifying stakeholders about a deployment. 'Announce' is also common but more public-facing; 'share' is informal; 'broadcast' implies mass distribution to a very wide audience.