Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update CHANGELOG for 17.03.0-ce #31205

Merged
merged 1 commit into from
Feb 22, 2017
Merged

Conversation

vieux
Copy link
Contributor

@vieux vieux commented Feb 21, 2017

@vieux vieux added this to the 17.03.0 milestone Feb 21, 2017
@vieux vieux self-assigned this Feb 21, 2017
@aaronlehmann
Copy link
Contributor

We need to mention and explain the versioning change.

Here are changelog entries for swarm mode changes:

And another networking one:

@vieux vieux force-pushed the update_changelog_17.03 branch from bc5452b to ffbd42c Compare February 21, 2017 22:01
@vieux
Copy link
Contributor Author

vieux commented Feb 21, 2017

@aaronlehmann @mavenugo @thaJeztah PTAL

@vieux
Copy link
Contributor Author

vieux commented Feb 21, 2017

ping @friism

@friism
Copy link
Contributor

friism commented Feb 21, 2017

(not maintainer) lgtm!

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mavenugo
Copy link
Contributor

LGTM

CHANGELOG.md Outdated
@@ -7,24 +7,41 @@ be found.

## 17.03.0-ce (2017-03-01)

**IMPORTANT**: Starting with this release, Docker is on a monthly release cycle and uses a
new YY.MM versioning scheme to reflect this. In addition to a monthly release, more stable
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if "more stable" is the right terminology here. Even as a maintainer, I don't quite understand this. Are we saying that the monthly releases are bleeding edge, and shouldn't be run by users that value stability, but the quarterly releases will be somehow better? Or do we mean to say that the quarterly releases will be supported for a longer period? (I actually don't know the answer here.)

How can users distinguish a "monthly" release from a "quarterly" release?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this should say: "Two channels are available: monthly and quarterly. Any given monthly release will only receive security and bugfixes until the next monthly release is available. Quarterly releases receive security and bugfixes for 4 months after initial release."

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated PTAL, regarding How can users distinguish a "monthly" release from a "quarterly" release? I think we need some sort a graph

Signed-off-by: Victor Vieux <victorvieux@gmail.com>
@vieux vieux force-pushed the update_changelog_17.03 branch from ffbd42c to fa43a64 Compare February 22, 2017 20:03
@aaronlehmann
Copy link
Contributor

LGTM

@vieux vieux changed the title [WIP] update CHANGELOG for 17.03.0-ce update CHANGELOG for 17.03.0-ce Feb 22, 2017
@vieux vieux merged commit 9fb5c83 into moby:17.03.x Feb 22, 2017
@vieux vieux deleted the update_changelog_17.03 branch February 22, 2017 23:05
@ralphtheninja
Copy link
Contributor

Hi. Where can I read up on the new versioning scheme?

thaJeztah pushed a commit to thaJeztah/docker that referenced this pull request Mar 6, 2017
update CHANGELOG for 17.03.0-ce
(cherry picked from commit 9fb5c83)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants