p4u1/docker-cli

Files

History

Sebastiaan van Stijn 5afda05713 Release checklist - bump versions earlier

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>
Upstream-commit: 354dabf3cafa89634057f42d1490fb1b1e3f8963
Component: engine

2016-02-04 23:45:49 +01:00

..

ARM.md

add support for building first ARM debian package

2016-01-29 00:21:17 +01:00

BRANCHES-AND-TAGS.md

Document branches and tags

2015-07-24 16:56:30 -07:00

CONTRIBUTORS.md

Move 'hack' to the less confusing 'project'

2014-11-09 21:50:28 +00:00

GOVERNANCE.md

HTTPS urls for ./project

2015-04-11 13:58:09 -04:00

IRC-ADMINISTRATION.md

Carry of PR #13520

2015-06-13 09:27:30 -07:00

ISSUE-TRIAGE.md

Remove Fedora 21 from RPM build as it is EOL

2015-12-20 00:42:17 +01:00

PACKAGE-REPO-MAINTENANCE.md

make docs better for scripts as well

2016-01-27 15:57:24 -08:00

PACKAGERS.md

*: remove documentation references to dockerinit

2016-01-26 23:47:02 +11:00

PATCH-RELEASES.md

Document process for patch-releases

2015-12-19 14:49:49 +01:00

PRINCIPLES.md

minor grammar suggestion

2015-02-18 16:26:24 +00:00

README.md

Add links and correct locations in project/README.md

2015-07-22 16:31:12 -04:00

RELEASE-CHECKLIST.md

Release checklist - bump versions earlier

2016-02-04 23:45:49 +01:00

RELEASE-PROCESS.md

Documenting Docker release process

2015-08-06 11:42:27 -07:00

REVIEWING.md

add new impact/distribution label

2015-12-30 13:53:46 +01:00

TOOLS.md

Fix TOOLS.md jenkins plugin link :)

2016-01-27 16:33:20 +01:00

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.