Skip to content

Operator version 3.1.1 #2108

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

Merged
merged 4 commits into from
Dec 17, 2020
Merged

Operator version 3.1.1 #2108

merged 4 commits into from
Dec 17, 2020

Conversation

rjeberhard
Copy link
Member

This is a draft PR tracking the preparation for a 3.1.1 bugfix release.

Let's make sure now that we have all of the necessary "3.1.0" to "3.1.1" changes and that the description of this bug fix change in this release is sufficient.

The bug fix itself is not yet present in this PR.

Copy link
Member

@rosemarymarano rosemarymarano left a comment

Choose a reason for hiding this comment

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

LGTM
(In a side note (and I imagine that you are aware of this), the documentation for prior releases of the operator stops at 2.6.0. It's a bummer but I think we need the most recent past docs much more so than the older ones.)

…agedServerUpAfterStep is executed after servers in all clusters started. (#2109)
@rjeberhard rjeberhard marked this pull request as ready for review December 17, 2020 18:52
@rjeberhard rjeberhard merged commit 59c6083 into master Dec 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants