kubernetes1.7 officially released

Historical Review of Kubernetes release

Kubernetes 1.0-July 2015 released

Kubernetes 1.1-November 2015 released

Kubernetes 1.2-March 2016 released

Kubernetes 1.3-July 2016 released

Kubernetes 1.4-September 2016 released

Kubernetes 1.5-December 2016 released

Kubernetes 1.6-March 2017 release Kubernetes1.7 release plan

April 3, 2017, start writing 1.7 code

April 6, 2017, release v1.7.0-alpha.1 version

April 19, 2017, release v1.7.0-alpha.2 version

May 1, 2017, 1.7 version features freeze discussion in Git Library

May 3, 2017, release v1.7.0-alpha.3 version

May 17, 2017, release v1.7.0-alpha.4 version

May 31, 2017, release v1.7.0-beta.0 version

June 1, 2017, 1.7 version feature code freeze

June 7, 2017, release v1.7.0-beta.1 version

June 14, 2017, release v1.7.0-beta.2 version

June 19, 2017, release v1.8.0-alpha.1 version

June 21, 2017, released v1.7 RC version

June 28, 2017, official release of the v1.7.0 GA version (which was actually released on June 30 in GitHub) Phase I: April 3, 2017--May 31, 2017 (completed)

These 8 weeks to write 1.7 code

Release 1.7 of an alpha version every two weeks

April 6, 2017, release v1.7.0-alpha.1 version

April 19, 2017, release v1.7.0-alpha.2 version

May 1, 2017, 1.7 version features freeze discussion in Git library

May 3, 2017, release v1.7.0-alpha.3 version

May 17, 2017, release v1.7.0-alpha.4 version

May 31, 2017, release v1.7.0-beta.0 version

1. Create a publishing branch

2. Configure continuous integration for this new branch

3. Continuous integration at least once a day Phase II: June 1, 2017-June 15, 2017 (completed)

June 1: Feature code freezes

1.1.7 Characteristics related PR termination submission

2. Add milestone constraints to the already submitted feature PR

3. The community is expected to convene two or three feature burn-down meetings, which will be held every day during the 1.7 official release of the week. Users who are interested in this can join Google Group for viewing.

4. Focus on fixing bugs, testing defects, testing stability

5. To ensure that the 1.7 version of the relevant documentation and release Guide are all finished

6. Determine that all features are included in the 1.7 release and that the Alpha, Beta, GA versions are identified in the Git library.

June 7: Release v1.7.0-beta.1 version (finished)

June 14: Release v1.7.0-beta.2 version

1. Perform the last fast-forward operation on the 1.7 release branch.

2. All modifications made for release 1.7 must be in bulk by the publishing branch manager git Cherry-pick.

3. Delete the milestone constraints on the submitted feature PR. The whole weekend collation accumulated down the PR. Phase III: June 19, 2017-June 28, 2017 (completed)

June 19: Release v1.8.0-alpha.1 version

June 21: Release v1.7 RC version

1. The RC version means that there is no known block problem.

2. Only accept the Git cherry-pick operation of the publishing administrator.

3. Notify Twitter users via mail group, so that users can use the 1.7RC version.

4. Users within the community may be able to get a 1.7RC version earlier.

5. More RC versions may be released for validation prior to GA release.

June 28: Official release of the 1.7 GA version (which was actually released on June 30 in GitHub) v1.7.0 some new features

From the view of Changelog, in v1.7.0, the kubenetes has been safely strengthened, and the Statefulset and Daemonset have been enhanced.