English for Code Freeze Announcements: Clear Wording That Avoids Confusion
Learn the exact English phrasing to announce a code freeze or embargo clearly — dates, scope, exceptions and escalation paths — with templates and before/after rewrites.
A code freeze is one of those announcements where ambiguity costs real money. If half the team thinks the freeze starts Friday and the other half thinks it starts Monday, you get a last-minute merge that breaks the release. The English you use has to be precise, scannable, and impossible to misread.
This guide gives you the vocabulary, structure, and templates to announce a code freeze (or embargo) in clear professional English.
What a code freeze announcement must answer
Every reader skims your message looking for five facts. If any one is missing, you will get follow-up questions in your inbox.
- What is frozen (the scope: which repos, branches, services)
- When the freeze starts and ends (with timezone)
- Why the freeze is happening (release, audit, incident)
- What is still allowed (the exceptions)
- Who to contact to get an exception approved
A good announcement is structured so a reader finds all five in under ten seconds.
Core vocabulary
- Code freeze — a period when no new code may be merged.
- Feature freeze — only bug fixes allowed; no new features.
- Hard freeze vs soft freeze — a hard freeze blocks all changes; a soft freeze discourages them but allows exceptions.
- Embargo — a hold on releasing or disclosing something (often security-related) until a set date.
- Cutoff — the deadline after which changes are no longer accepted. “The cutoff is 18:00 UTC.”
- To lift a freeze — to end it. “The freeze will be lifted on Monday.”
- Exception / carve-out — a change allowed despite the freeze.
- To escalate — to ask a higher authority to approve something.
Note the verb pairs: a freeze is imposed, enforced, and finally lifted. Avoid “open” or “close” the freeze — they sound wrong to native ears.
Get the tense and modality right
Announcements describe future rules, so you lean on the present simple for facts and modal verbs for permissions.
- will be for scheduled facts: “The freeze will be in effect from Friday 17:00.”
- must / must not for hard rules: “You must not merge to
mainduring the freeze.” - may for permitted exceptions: “Critical hotfixes may be merged with approval.”
- should for strong recommendations that aren’t absolute: “You should merge any open PRs before the cutoff.”
A common mistake is mixing “cannot” and “must not”. Use must not for a rule you are imposing; use cannot only when it is technically impossible.
Weak: “Please try not to merge things this weekend if possible.” Strong: “Do not merge to
mainbetween Friday 17:00 and Monday 09:00 UTC. Hotfixes require approval from @oncall.”
A reusable template
Subject: [CODE FREEZE] main branch — Fri 14 Jun 17:00 to Mon 17 Jun 09:00 UTC
What: Code freeze on the `main` branch of payments-api and checkout-web.
When: Friday 14 June 17:00 UTC → Monday 17 June 09:00 UTC.
Why: We are cutting the 4.2 release and need a stable branch for QA.
During the freeze:
- Do NOT merge to `main`.
- Feature branches are unaffected — keep working there.
- CI will block merges automatically.
Exceptions:
- Only Sev-1 / Sev-2 hotfixes.
- Request approval from @release-captain in #releases before merging.
Questions: reply here or ping @release-captain.This works because the reader can answer all five questions without reading a full paragraph.
Phrases for each section
Opening (state the rule up front):
- “We are imposing a code freeze on
mainfrom … to ….” - “
mainwill be frozen for the 4.2 release between … and ….”
Scope (be explicit about what is and isn’t included):
- “This freeze applies to
mainonly; feature branches are unaffected.” - “The freeze covers all services in the
checkoutnamespace.”
Exceptions:
- “Only Sev-1 and Sev-2 hotfixes will be considered.”
- “Exceptions must be approved by the release captain before merging.”
- “If you believe your change qualifies for a carve-out, raise it in #releases.”
Escalation:
- “To request an exception, ping @release-captain with the PR link and a one-line justification.”
Closing / lift:
- “The freeze will be lifted once QA signs off on the release candidate.”
- “We’ll post here the moment the freeze is lifted.”
Announcing a security embargo
Embargoes need slightly different language because the reason often can’t be shared.
“We are placing an embargo on the
auth-fixbranch until Tuesday 18 June, 09:00 UTC, when the coordinated disclosure goes public. Please do not push these commits to public forks, discuss the issue in public channels, or reference the CVE before that time. Direct questions to the security team in #secops.”
Key phrases:
- “under embargo until …”
- “coordinated disclosure”
- “Please do not discuss this publicly before the embargo lifts.”
Before and after
Before: “Hey all, we’re going to freeze things soon for the release, so maybe wrap up your work? Let me know if you need to merge something important.”
The reader doesn’t know when “soon” is, what “things” means, or how to ask for an exception.
After: “[CODE FREEZE]
mainis frozen from Fri 17:00 to Mon 09:00 UTC for the 4.2 release. Merge open PRs before 17:00. Only Sev-1/Sev-2 hotfixes allowed — ping @release-captain for approval. Feature branches are unaffected.”
Same length, infinitely clearer.
Common mistakes
- Vague timing. “End of the week” or “soon” — always give a date and timezone.
- No timezone. “17:00” means three different things across your team. Use UTC or label the zone.
- Burying the rule. Don’t open with three sentences of context. Lead with the rule.
- Forgetting the lift. People need to know when normal work resumes. Always state the end.
- “freeze the code” vs “code freeze”. As a noun, it’s code freeze. As a verb, we are freezing
main.
Key takeaways
- Answer five questions: what, when, why, exceptions, contact.
- Lead with the rule; put context second.
- Use must not for hard rules, may for exceptions, should for recommendations.
- Always give dates and a timezone.
- State when the freeze will be lifted — don’t leave people guessing.
A clear freeze announcement is a small piece of writing with an outsized impact on your release. Master the template above and you’ll never field a “wait, has the freeze started?” message again.