Release branches are created for solving bugs detected after the application is released to the user
Answers
Answer:
True
Explanation:
The method of reasoning is that these bugs ought to be little things that identify with the discharge, and it will improve your discharge test cycle by maintaining a strategic distance from bug-fix branches. While the method of reasoning is sound, I trust it's smarter to ensure the codebase is secured, and code survey procedures ought not to be subverted in light of the fact that a discharge needs to go out the entryway. Since you have a code survey strategy, make a bug-fix include branch off your discharge branch, focus on the bug-fix branch and present a PR from bug-fix branch to discharge branch- paying little respect to what the docs state. All things considered, the branch system ought to be custom-made to your requirements, not a different way.