354dabf3ca
Bump both API and VERSION directly after the release branch is created. All changes to master after that are (by default) for the *next* release. Signed-off-by: Sebastiaan van Stijn <github@gone.nl> |
||
|---|---|---|
| .. | ||
| ARM.md | ||
| BRANCHES-AND-TAGS.md | ||
| CONTRIBUTORS.md | ||
| GOVERNANCE.md | ||
| IRC-ADMINISTRATION.md | ||
| ISSUE-TRIAGE.md | ||
| PACKAGE-REPO-MAINTENANCE.md | ||
| PACKAGERS.md | ||
| PATCH-RELEASES.md | ||
| PRINCIPLES.md | ||
| README.md | ||
| RELEASE-CHECKLIST.md | ||
| RELEASE-PROCESS.md | ||
| REVIEWING.md | ||
| TOOLS.md | ||
README.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.