vbatts/registry
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Merge pull request #1 from amylindburg/patch-1

Browse source 
recast text of the page
This commit is contained in:
Stephen Day 2015-03-18 19:12:47 -07:00
commit b1232a92e7
1 changed files with 43 additions and 46 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

83
ROADMAP.md
View file

@ -1,10 +1,12 @@
# Roadmap # Roadmap
This document covers the high-level the goals and dates for features in the The Distribution Project consists of several components, some of which are still being defined. This document defines the high-level goals of the project, identifies the current components, and defines the release-relationship to the Docker Platform.
docker registry. The distribution project currently has several components to
report in the road map, which are covered below.
## Goals * [Distribution Goals](#distribution-goals)
* [Distribution Components](#distribution-components)
* [Project Planning](#project-planning): release-relationship to the Docker Platform.
## Distribution Goals
- Replace the existing [docker registry](github.com/docker/docker-registry) - Replace the existing [docker registry](github.com/docker/docker-registry)
implementation as the primary implementation. implementation as the primary implementation.
@ -13,30 +15,27 @@ report in the road map, which are covered below.
- Define a strong data model for distributing docker images - Define a strong data model for distributing docker images
- Provide a flexible distribution tool kit for use in the docker platform - Provide a flexible distribution tool kit for use in the docker platform
## Components ## Distribution Components
The distribution project has a few components with independent road maps and Components of the Distribution Project are managed via github [milestones](https://github.com/docker/distribution/milestones). Upcoming
road maps related to the docker project. They are covered below. features and bugfixes for a component will be added to the relevant milestone. If a feature or
### Registry
The current status of the registry road map is managed via github
[milestones](https://github.com/docker/distribution/milestones). Upcoming
features and bugfixes will be added to relevant milestones. If a feature or
bugfix is not part of a milestone, it is currently unscheduled for bugfix is not part of a milestone, it is currently unscheduled for
implementation. implementation.
The high-level goals for each registry release are part of this section. * [Registry](#registry)
* [Distribution Package](#distribution-package)
#### 2.0 ***
Milestones: [2.0.0-beta](https://github.com/docker/distribution/milestones/Registry/2.0.0-beta) [2.0.0-rc](https://github.com/docker/distribution/milestones/Registry/2.0.0-rc) [2.0.0](https://github.com/docker/distribution/milestones/Registry/2.0.0) ### Registry
The 2.0 release is the first release of the new registry. This is mostly Registry 2.0 is the first release of the next-generation registry. This is primarily
focused on implementing the [new registry focused on implementing the [new registry
API](https://github.com/docker/distribution/blob/master/doc/spec/api.md) with API](https://github.com/docker/distribution/blob/master/doc/spec/api.md), with
a focus on security and performance. a focus on security and performance.
#### Registry 2.0
Features: Features:
- Faster push and pull - Faster push and pull
@ -50,9 +49,7 @@ Features:
- Pluggable authentication system - Pluggable authentication system
- Health Checks ([#230](https://github.com/docker/distribution/pull/230)) - Health Checks ([#230](https://github.com/docker/distribution/pull/230))
#### 2.1 #### Registry 2.1
Milestone: [2.1](https://github.com/docker/distribution/milestones/Registry/2.1)
Planned Features: Planned Features:
@ -62,33 +59,33 @@ Planned Features:
- Mirroring ([#19](https://github.com/docker/distribution/issues/19)) - Mirroring ([#19](https://github.com/docker/distribution/issues/19))
- Flexible client package based on distribution interfaces ([#193](https://github.com/docker/distribution/issues/193) - Flexible client package based on distribution interfaces ([#193](https://github.com/docker/distribution/issues/193)
#### 2.2 #### Registry 2.2
Milestone: [2.2](https://github.com/docker/distribution/milestones/Registry/2.2)
TBD TBD
### Docker Platform ***
To track various requirements that must be synced with releases of the docker ### Distribution Package
platform, we've defined labels corresponding to upcoming releases. Each
release also has a project page explaining the relationship of the
distribution project with the docker project.
Please see the following table for more information: At its core, the Distribution Project is a set of Go packages that make up
Distribution Components. At this time, most of these packages make up the
Registry implementation.
| Platform Version | Milestone | Project | The package itself is considered unstable. If you're using it, please take care to vendor the dependent version.
|-----------|------|-----|
| Docker 1.6 | [Docker/1.6](https://github.com/docker/distribution/labels/docker%2F1.6) | [Project](https://github.com/docker/distribution/wiki/docker-1.6-Project-Page) |
| Docker 1.7| [Docker/1.7](https://github.com/docker/distribution/labels/docker%2F1.7) | [Project](https://github.com/docker/distribution/wiki/docker-1.7-Project-Page) |
| Docker 1.8| [Docker/1.8](https://github.com/docker/distribution/labels/docker%2F1.8) | [Project](https://github.com/docker/distribution/wiki/docker-1.8-Project-Page) |
### Package For feature additions, please see the Registry section. In the future, we may break out a
separate Roadmap for distribution-specific features that apply to more than
The distribution project, at its core, is a set of Go packages that make up
distribution components. At this time, most of these packages make up the
registry implementation. The package itself is considered unstable. If you're
using it, please take care to vendor the dependent version. For feature
additions, please see the Registry section. In the future, we may break out a
separate road map for distribution specific features that apply to more than
just the registry. just the registry.
***
### Project Planning
Distribution Components map to Docker Platform Releases via the use of labels. Project Pages are used to define the set of features that are included in each Docker Platform Release.
| Platform Version | Label | Planning |
|-----------|------|-----|
| Docker 1.6 | [Docker/1.6](https://github.com/docker/distribution/labels/docker%2F1.6) | [Project Page](https://github.com/docker/distribution/wiki/docker-1.6-Project-Page) |
| Docker 1.7| [Docker/1.7](https://github.com/docker/distribution/labels/docker%2F1.7) | [Project Page](https://github.com/docker/distribution/wiki/docker-1.7-Project-Page) |
| Docker 1.8| [Docker/1.8](https://github.com/docker/distribution/labels/docker%2F1.8) | [Project Page](https://github.com/docker/distribution/wiki/docker-1.8-Project-Page) |