Does the code hang with Git?

Question

In the context of Git's advantages (objectivity) over SVN, do simpler Git merge / fork functions make code freeze when using Git (or equivalent)? Did you understand the concept of code freezing because merging later is so complicated?

I understand that this may be a subjective question, but I really want to know if the phrase "code freeze" is outdated or indicates a project that is not forked or merged. If you could branch and merge automatically, would you ever code a freeze? I don’t think it would be so, because you could localize the topic / function branch and continue development, knowing that merging would be easy.

Answer 1

Although it’s true that you can continue to do function and “risky” development, simple branching and merging does not become obsolete.

You either freeze the release branch and hope that people will work on it anyway or freeze the wizard and hope that more people will help in eliminating and polishing the final release blockers (they are practically forced if they do not know SCM well).

In addition to the quality of the release code, code hangs are crucial for translators, since code freezing is usually accompanied by line freezing, after which it ultimately makes sense to completely fix the translations.

Answer 2

This has nothing to do with how easy it is to combine change. The goal of freezing is to stop development on a stable release. When freezing, you only correct errors. You do not want the code to merge automatically because it could have unverified code and introduce errors. Usually you mark a freeze and grow in a trunk / branch to the next version.

Answer 3

It depends on what “code freeze” means.

If you mean that everyone switches to error compression mode. -- why not? mistakes always need some love.

If you think that everyone is doing nothing and waiting for the QA team. - No, this is not related to git.