b75aa9ace9
I believe that it is helpful to build the binary first. That way, if you interrupt the tests, you still get a binary to play with. If you run the tests first and interrupt them, no binary for you! Also, the second part of this commit is an undeniable proof that Bash array syntax is nothing else than an elaborate troll by Bash authors. Upstream-commit: 85956c70b5613439d9f239550c5c4ec360339cb6 Component: engine
Hacking on Docker
The hack/ 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.md.
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
make.sh is the primary build tool for docker. It is used for compiling the official binary, running the test suite, and pushing releases.