To cut a release means to create a release build from the codebase at a chosen point, branching or tagging it. It is the established collocation: "cut the 2.0 release from main". "Slice", "chop off", and "carve" are not used. Cut pairs with release and branch, and marks the moment the code is frozen for shipping.
2 / 5
Before publishing we ___ the commit so we can reference it later.
To tag a version means to attach a named marker (like v1.4.0) to a specific commit in version control. It is the standard collocation: "tag the release commit". "Label", "mark over", and "name out" are not the precise term in Git. Tag pairs with version, commit, and release, and gives every release an immutable, referenceable point.
3 / 5
The release manager will ___ release notes summarising the changes.
To draft release notes means to write an initial version describing what changed in a release. It is the natural collocation: "draft the release notes from merged PRs". "Sketch up", "rough", and "pen over" are not idiomatic in this context. Draft pairs with release notes, changelog, and announcement, and implies a first version that may be polished before publishing.
4 / 5
We finally ___ the new search feature to all users today.
To ship a feature means to release it to users. It is one of the most common collocations in software culture: "we shipped dark mode". "Post", "mail", and "float" do not carry this meaning. Ship pairs with feature, release, and code, and conveys delivering finished work into production.
5 / 5
A critical bug appeared, so we pushed a ___ overnight.
A hotfix is an urgent patch applied to fix a serious problem in production, often outside the normal release cycle. We say "ship a hotfix" or "hotfix the bug". "Quickfix patch", "warmfix", and "fastfix" are not standard. Hotfix works as both noun and verb and signals speed and urgency in the release process.