Code Freezes can have the opposite effect

JensRantil 13 points 3 comments April 05, 2026
jensrantil.github.io · View on Hacker News

Discussion Highlights (2 comments)

trustfixsec

Lived this many times. the worst part about these freezes is what happens right before the freeze - everyone will rush to push their changes prior to cutoff, which is exactly when you get the sloppiest commits. and then after the freeze lifts you get a flood of piled up changes all at once. Smaller, continuous deploys with a good rollback are way less risky than big batched releases after a freeze.

WolfeReader

I cannot fathom why anyone would use a code freeze. Just create a branch at the commit you want to "freeze" and let dev teams keep working with their regular branches.

Semantic search powered by Rivestack pgvector
3,663 stories · 34,065 chunks indexed