(Cross posted from its original source) ‘Tis the season that one of my favorite blog posts gets pulled out and put in rotation, much like “White Christmas” on the radio station. I’m speaking, of course, of “Friday Deploy Freezes are Exactly Like Murdering Puppies” (old link on WP). This feels like as good a time…

Charity's platform is a central hub for nonprofit organizations, volunteers, and philanthropists, offering insights into charitable initiatives, fundraising strategies, and social impact projects. Through articles, success stories, and fundraising guides, Charity offers insights into effective nonprofit management, donor engagement, and community outreach efforts. Readers can learn about nonprofit governance, grant writing, and advocacy campaigns to support causes they care about and make a positive difference in the world.

Charity

Deploy freezes during holidays or weekends are pragmatic workarounds for teams lacking robust observability, not virtues to celebrate. The better approach is freezing merges instead of deploys to prevent snowballing changes, and continuing to run the deploy process without shipping new code to catch systemic issues that emerge from deployment inactivity. Teams with high-quality observability can maintain deployment velocity while reducing change rate during holiday periods.

On Friday Deploys: Sometimes that Puppy Needs Murdering (xpost)

Don’t freeze deploys unless your goal is to test deploy freezes