8.2 Handling Release Branches
Release branches are a place to prepare code for a release. Teams normally use them to segregate code for a release. What segregate means depends on the team.
The exact timing of a release branch depends on the team and your development style. For simplicity’s sake, let’s work with this definition: a release branch is created when a project is feature complete—that is, it has everything it needs to satisfy this release—but hasn’t been fully vetted yet.
This type of branch will have only minimal changes made to it,
and all will focus around fixes, whether they are bugs or logic,
but no new features are added. These release branches make
it easy to continue developing new features on the
master branch while the ...
Get Pragmatic Version Control Using Git now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
