About Docker CE
About Docker CE
Docker Community Edition (CE) is ideal for developers and small teams looking to get started with Docker and experimenting with container-based apps. Docker CE has three types of update channels, stable, test, and nightly:
Stable gives you latest releases for general availability.
Test gives pre-releases that are ready for testing before general availability.
Nightly gives you latest builds of work in progress for the next major release.
For more information about Docker CE, see Docker Community Edition.
关于Docker CE
Docker Community Edition（CE）非常适合希望开始使用Docker并尝试使用基于容器的应用程序的开发人员和小型团队。 Docker CE有三种类型的更新通道：stable，test和nightly：
Stable为您提供一般可用性的最新版本。
Test提供在一般可用之前准备好进行测试的预发布。
Nightly为您提供下一个主要版本的最新正在进行的工作。
有关Docker CE的更多信息，请参阅Docker Community Edition。
Releases
For the Docker CE engine, the open repositories Docker Engine and Docker Client apply.
Releases of Docker Engine and Docker Client for general availability are versioned using dotted triples. The components of this triple are YY.mm. where the YY.mmcomponent is referred to as the year-month release. The version numbering format is chosen to illustrate cadence and does not guarantee SemVer, but the desired date for general availability. The version number may have additional information, such as beta and release candidate qualifications. Such releases are considered “pre-releases”.
The cadence of the year-month releases is every 6 months starting with the 18.09release. The patch releases for a year-month release take place as needed to address bug fixes during its support cycle.
Docker CE binaries for a release are available on download.docker.com as packages for the supported operating systems. Docker EE binaries are available on the Docker Storefor the supported operating systems. The release channels are available for each of the year-month releases and allow users to “pin” on a year-month release of choice. The release channel also receives patch releases when they become available.
发布
对于Docker CE引擎，应用开放存储库Docker Engine和Docker Client。
Docker Engine和Docker Client的一般可用性版本使用由点隔开的三个元组进行版本控制。这个三元组的组件是YY.mm.
从18.09发布开始，发布的周期是每6个月一次。根据需要发布的补丁版本，以解决其支持周期中的错误修复问题。
发行版的Docker CE二进制文件可从download.docker.com获得，作为支持的操作系统的软件包。 Docker Store上提供了Docker EE二进制文件，用于支持的操作系统。发布渠道适用于每个月的版本，并允许用户选择“固定”年度的发布。发布渠道在变得可用时也会收到补丁发布。
Nightly builds
Nightly builds are created once per day from the master branch. The version number for nightly builds take the format 0.YYYYmmdd.HHMMSS, for example 0.20181231.093045. These builds allow for testing from the latest code on the master branch. No qualifications or guarantees are made for the nightly builds.
The release channel for these builds is called nightly.
Nightly构建
Night每天从主分支创建一次构建。 Nightlky构建的版本号采用0.YYYYmmdd.HHMMSS格式，例如0.20181231.093045。 这些构建允许从主分支上的最新代码进行测试。 构建Nightlys没有任何资质或保证。
为这些构建而发布通道称为Ngihtly。
Pre-releases
In preparation for a new year-month release, a branch is created from the master branch with format YY.mm when the milestones desired by Docker for the release have achieved feature-complete. Pre-releases such as betas and release candidates are conducted from their respective release branches. Patch releases and the corresponding pre-releases are performed from within the corresponding release branch.
While pre-releases are done to assist in the stabilization process, no guarantees are provided.
Binaries built for pre-releases are available in the test channel for the targeted year-month release using the naming format test-YY.mm, for example test-18.09.
预发布
为了准备新的year-month发布，当Docker实现了完成功能的里程碑时，将从主分支创建一个分支，格式为YY.mm。 诸如测试版和发布候选版本的预发布版本从其各自的发布分支机构进行。 补丁版本和相应的预发布版本在相应的发布分支中执行。
然而预发布是为了协助稳定过程，但不提供任何保证。
为预发布year-month版本构建的二进制文件可在测试通道中使用命名格式test-YY.mm（例如test-18.09）。
General availability
Year-month releases are made from a release branch diverged from the master branch. The branch is created with format 18.09. The year-month name indicates the earliest possible calendar month to expect the release to be generally available. All further patch releases are performed from that branch. For example, once v18.09.0 is released, all subsequent patch releases are built from the 18.09 branch.
Binaries built from this releases are available in the stable channel stable-YY.mm, for example stable-18.09, as well as the corresponding test channel.
一般可用性
Year-month发布是从与主分支分开的发布分支进行的。 分支以格式
从此版本构建的二进制文件可在稳定通道stable-YY.mm中获得，例如stable-18.09，以及相应的测试通道。
Relationship between CE and EE code
For a given year-month release, Docker releases both CE and EE variants concurrently. EE is a superset of the code delivered in CE. Docker maintains publicly visible repositories for the CE code as well as private repositories for the EE code. Automation (a bot) is used to keep the branches between CE and EE in sync so as features and fixes are merged on the various branches in the CE repositories (upstream), the corresponding EE repositories and branches are kept in sync (downstream). While Docker and its partners make every effort to minimize merge conflicts between CE and EE, occasionally they will happen, and Docker will work hard to resolve them in a timely fashion.
CE与EE代码之间的关系
对于给定的年度版本，Docker同时发布CE和EE变体。 EE是CE中提供的代码的超集。 Docker维护CE代码的公开可见存储库以及EE代码的私有存储库。 自动化（机器人）用于使CE和EE之间的分支保持同步，以便在CE存储库（上游）的各个分支上合并特征和修复，相应的EE存储库和分支保持同步（下游）。 虽然Docker及其合作伙伴尽一切努力减少CE和EE之间的合并冲突，但偶尔会发生这种冲突，Docker将努力及时解决它们。