Freeze (software engineering)

From Wikipedia, the free encyclopedia

In software engineering, a freeze represents a point in time in the development process after which the rules for making changes to the source code or related resources become more strict. A freeze helps move the project forward towards a release or the end of an iteration. The stricter rules may include only allowing changes which fix bugs, or allowing changes only after thorough review by other members of the development team.

A particular kind of freeze is feature freeze, when all work on adding new features is suspended, shifting the effort towards fixing bugs and improving the user experience.

[edit] See also

Software spanner This software engineering-related article is a stub. You can help Wikipedia by expanding it.
Languages