e580f885da0b0dabeb691bf09e256b9a6eb62819
Rather than keeping a branch named "release" where we merge every release, we want to keep "disposable" release branches for each release. This will make much easier to create new major releases, since we always want to start these releases from what we have in master. We create a disposable release branch from master that we'll only use during the lifecycle of the major release. Once the release branch is created, the release captain will use a "bump" branch in her own fork to cherry pick changes that will need to be applied to this release. We'll track those changes in a pull request between the disposable release branch and the bump branch. Signed-off-by: David Calavera <david.calavera@gmail.com> Upstream-commit: bca8159174f05b40e7d4379142052f4200987654 Component: engine
Description
No description provided
Languages
Go
92%
Shell
5.5%
Dockerfile
1.1%
Go-Checksums
0.9%
Makefile
0.3%
Other
0.2%