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

Release planning for March #9411

Closed
25 tasks done
gyuho opened this issue Mar 8, 2018 · 11 comments
Closed
25 tasks done

Release planning for March #9411

gyuho opened this issue Mar 8, 2018 · 11 comments

Comments

@gyuho
Copy link
Contributor

gyuho commented Mar 8, 2018

Most of items are already addressed. Just to not forget.



/cc @jpbetz

@jpbetz
Copy link
Contributor

jpbetz commented Mar 8, 2018

I'm in favor of getting #9364 in, ideally all the way back to v3.1.12 (since we're releasing it). But I haven't been involved closely enough to make a careful assessment of the risk. @wojtek-t, @mborsz what do you think?

@jpbetz
Copy link
Contributor

jpbetz commented Mar 8, 2018

I'm available this afternoon (1pm-) to do the 3.1 and 3.2 releases. I'll submit the remaining backport requests shortly.

@gyuho
Copy link
Contributor Author

gyuho commented Mar 8, 2018

But I haven't been involved closely enough to make a careful assessment of the risk

Yeah, it would be great if someone else can cross-check #9364.

Also to clarify, ideally we get all fixes in and publish releases, by today. But if it takes longer, I am also available next week as well. I just cannot sign the binaries, but can still push official release images.

@wojtek-t
Copy link
Contributor

wojtek-t commented Mar 8, 2018

+1 for waiting for #9364 if that's possible.

@jpbetz
Copy link
Contributor

jpbetz commented Mar 8, 2018

Current thinking is that we'll release v3.1.12, v3.2.17, v3.3.2 today without #9364 and then aim for an additional set of releases next week for #9364 once we've validated the latest changes against GKE and any other use cases we can find.

@gyuho
Copy link
Contributor Author

gyuho commented Mar 8, 2018

I will be working on simpler solution for #9333. Once we test it, we can backport to release branches.

@wojtek-t
Copy link
Contributor

wojtek-t commented Mar 9, 2018

Current thinking is that we'll release v3.1.12, v3.2.17, v3.3.2 today without #9364 and then aim for an additional set of releases next week for #9364 once we've validated the latest changes against GKE and any other use cases we can find.

SGTM

@jpbetz
Copy link
Contributor

jpbetz commented Mar 28, 2018

3.1.13 and 3.2.18 backports are merged.

@gyuho
Copy link
Contributor Author

gyuho commented Mar 28, 2018

@jpbetz Thanks!

I manually ran test suites (including functional tests) for 3.1 and 3.2, locally; all passed.
And 3.3 CI https://semaphoreci.com/coreos/etcd/branches/release-3-3/builds/65 passed.

We will publish releases tomorrow.

@gyuho
Copy link
Contributor Author

gyuho commented Mar 29, 2018

We've just published:

Please check the CHANGELOGs for all details.

@gyuho gyuho closed this as completed Mar 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants