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

CHANGELOG-3.2.md description confused about mininum recommended etcd versions #10669

Closed
Bevisy opened this issue Apr 23, 2019 · 1 comment · Fixed by #10694
Closed

CHANGELOG-3.2.md description confused about mininum recommended etcd versions #10669

Bevisy opened this issue Apr 23, 2019 · 1 comment · Fixed by #10694
Assignees

Comments

@Bevisy
Copy link

Bevisy commented Apr 23, 2019

CHANGELOG-3.2.md says the mininum recommended etcd versions is 3.1.11+, 3.2.26+, and 3.3.11+. But the provided mail group link says the mininum recommended etcd versions is 3.1.11+,3.2.10+,3.3.0+.
Is there some description that does not match?

@spzala
Copy link
Member

spzala commented Apr 30, 2019

@Bevisy The one in the CHANGELOG-3.2.md is the latest recommendation i.e. 3.1.11+, 3.2.26+, and 3.3.11+ I will update the .md files. Thanks! /cc @hexfusion

@spzala spzala self-assigned this Apr 30, 2019
spzala added a commit to spzala/etcd that referenced this issue Apr 30, 2019
Recommendations for the production were bumped up recently. The related
ML email ref is old one so we should not provide the link.

Fixes etcd-io#10669
spzala added a commit to spzala/etcd that referenced this issue May 10, 2019
Recommendations for the production were bumped up recently. The related
ML email ref is old one so we should not provide the link.

Fixes etcd-io#10669
hexfusion pushed a commit that referenced this issue May 11, 2019
Recommendations for the production were bumped up recently. The related
ML email ref is old one so we should not provide the link.

Fixes #10669
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants