A project manager recently told me that he wanted to implement a code freeze prior to user acceptance testing. This request struck me as odd since I don’t recall having implemented a code freeze on a project in years. My immediate response was that we do not need a code freeze. All checked in code is tested for its production readiness via a deployment pipeline.
The intent of a code freeze is to identify and lock down a known “good” state of the source code. The code can then be built, and then deployed from this known “good” state. If a developer checks in a change after a code freeze, then this known “good” state can be considered tainted. The intent behind implementing a code freeze is well placed, but the execution slows down a team’s progress.
The need to implement a code freeze demonstrates a lack of understanding…
View original post 143 more words