bca8159174
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> |
||
|---|---|---|
| .. | ||
| BRANCHES-AND-TAGS.md | ||
| CONTRIBUTORS.md | ||
| GOVERNANCE.md | ||
| IRC-ADMINISTRATION.md | ||
| ISSUE-TRIAGE.md | ||
| PACKAGERS.md | ||
| PRINCIPLES.md | ||
| README.md | ||
| RELEASE-CHECKLIST.md | ||
| REVIEWING.md | ||
| TOOLS.md | ||
Hacking on Docker
The project/ directory holds information and tools for everyone involved in the process of creating and
distributing Docker, specifically:
Guides
If you're a contributor or aspiring contributor, you should read CONTRIBUTORS.md.
If you're a maintainer or aspiring maintainer, you should read MAINTAINERS.
If you're a packager or aspiring packager, you should read PACKAGERS.md.
If you're a maintainer in charge of a release, you should read RELEASE-CHECKLIST.md.
Roadmap
A high-level roadmap is available at ROADMAP.md.
Build tools
hack/make.sh is the primary build tool for docker. It is used for compiling the official binary, running the test suite, and pushing releases.