title: Does codefreeze break the principles of continuous delivery?
body: <p>Following below git-flow,</p>
  
  <p><a href="https://i.stack.imgur.com/40YxC.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/40YxC.png" alt="enter image description here"></a></p>
  
  <hr>
  
  <p>Using CI/CD approach for SDLC, if a tagged commit passed QA pipeline, then it is time to  create <strong>Release branch</strong> from <strong>Develop branch</strong>, because my understanding is,</p>
  
  <p>If prod pipeline build fails on merge with <strong>Master branch</strong>, then developers need to fix that issue first and create a new working commit on the same <strong>Release</strong> branch. This may lead to code freeze time for developers to merge in <strong>Develop</strong> branch, for the reason, <strong>Release</strong> branch merge with <strong>Develop</strong> branch(after prod pipeline gives success) MUST not throw errors in dev pipeline.</p>
  
  <hr>
  
  <p>My question is, as shown below,</p>
  
  <p><a href="https://i.stack.imgur.com/7mjrz.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/7mjrz.png" alt="enter image description here"></a></p>
  
  <p>Does Master merge duration requires a code freeze time for other developers on <strong>Develop</strong> branch? If yes, Is codefreeze breaking the <a href="https://stackoverflow.com/questions/54172303/principles-of-continuous-delivery">principles</a> of continuous delivery?</p>