Freeze (software engineering)

<h2 id="implementations">Implementations</h2>
<p>In development environments using <a href="/facts/Version_control/pxCmFXqK">version control</a>, the use of <a href="/facts/Branching_(software)/1m0qK9tv">branching</a> can alleviate delays in development caused by freezes. For example, a project may have a "stable" branch from which new versions of the software are released, and a separate "development" branch in which the developers add new code. The effect of a freeze is then to prevent <i>promotion</i> of some or all changes from the development branch to the stable branch. In other words, the freeze applies only to the stable branch, and developers can continue their work on the development branch.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Feature_complete/UrzGvU0w">Feature complete</a></li>
<li><a href="/facts/Software_release_life_cycle/z4Q4RElA">Software release life cycle</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Mascitelli, Ronald (2007-01-01). The Lean Product Development Guidebook: Everything Your Design Team Needs to Improve Efficiency and Slash Time-to-market. Technology Perspectives. p. 111. ISBN 9780966269734. <a href="9780966269734" target="_blank">9780966269734</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
</ol>

Freeze (software engineering) open-in-new

Freeze (software engineering)