The document describes Chrome's release cycle, which aims for predictable, regular releases by adopting an overlapping development model. Key aspects include releasing every 6 weeks on 3 channels, addressing all work on a central trunk before branching for stabilization, and controlling scope by disabling unfinished features at branch points. This approach improved flow by making releases less draining and more predictable compared to long-lived branches and unpredictable cycles under the previous model.
The document describes Chrome's release cycle, which aims for predictable, regular releases by adopting an overlapping development model. Key aspects include releasing every 6 weeks on 3 channels, addressing all work on a central trunk before branching for stabilization, and controlling scope by disabling unfinished features at branch points. This approach improved flow by making releases less draining and more predictable compared to long-lived branches and unpredictable cycles under the previous model.