Mandatory Code freeze stage upon manual deployment

Code Freeze Period:

1 week after the end of each sprint so the assigned human resources can take a suitable amount of time to do the job.

---

A code freeze period shall begin which means Merging PRs that passed the code-review to the master-branch is not allowed at this stage, So the Testers (QA Stuff) can start their work effectively using the latest developed version (some people call it periodical release). It represents the completed working items AKA the total completed work represents in a collection of tickets deployed to testing environment via the Junior System Admins [Linux Based] if virtualization model is adopted OR via the Senior System Admins [Linux Based] if containerization model is adopted.

---

Note: Merging PRs to the master-branch is NOT allowed at this stage, whether:

• you do it via automated configuration and using a button to trigger that, or
• by agreement with the team to STOP
  • development which is done via Developers and
  • testing which is done via Testers [QA] and
  • daily standups meetings.