<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Change Freeze on SRE Engineering Practice</title><link>https://www.sre.wang/en/tags/change-freeze/</link><description>Recent content in Change Freeze on SRE Engineering Practice</description><image><title>SRE Engineering Practice</title><url>https://www.sre.wang/share-card-square.jpg</url><link>https://www.sre.wang/share-card-square.jpg</link></image><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 12 Sep 2026 10:29:05 +0800</lastBuildDate><atom:link href="https://www.sre.wang/en/tags/change-freeze/index.xml" rel="self" type="application/rss+xml"/><item><title>14-Day Change Freeze Still Blew Up P0: 5 Engineering Decisions from Manual Freeze to Dynamic Change Windows</title><link>https://www.sre.wang/en/posts/sre-change-freeze-dynamic-window/</link><pubDate>Sat, 12 Sep 2026 10:29:05 +0800</pubDate><guid>https://www.sre.wang/en/posts/sre-change-freeze-dynamic-window/</guid><description>Change freeze (code freeze) is no silver bullet. Starting from a real case where a 14-day freeze before Double 11 still resulted in a P0, this article breaks down 5 fatal flaws of manual freeze and provides 5 engineering decisions for moving to error-budget-driven dynamic change windows, with production-grade config examples and lessons learned.</description></item></channel></rss>