The stuff under "Freeze the code before release", such as a code freeze where devs can't make any changes, seems to be the opposite of the article's goal. Your

The stuff under "Freeze the code before release", such as a code freeze where devs can't make any changes, seems to be the opposite of the article's goal. Your release should be a specific commit ID, not a branch name, so it doesn't matter if people continue to develop and push changes. If you need to make changes specific to the release, use a release branch. No need to stop devs from moving on.