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

Mark the latest v1.19.x release as stable #2487

Merged
merged 1 commit into from
Nov 9, 2020

Conversation

brandond
Copy link
Member

@brandond brandond commented Nov 7, 2020

Proposed Changes

Mark the latest v1.19.x release as stable - final task from 2020-10-30 release checklist

Types of Changes

  • Channel

Verification

  • Install k3s from latest channel
  • Check version with k3s --version

Linked Issues

Related to #2460

Further Comments

@brandond brandond requested a review from a team as a code owner November 7, 2020 00:18
Copy link
Contributor

@davidnuzik davidnuzik left a comment

Choose a reason for hiding this comment

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

We can bump 1.18 but I thought we were not quite ready to mark v1.19.x as stable based on some recent conversations around SELinux? I thought we also wanted some more users to test out etcd.

FWIW my assumptions in that linked GH issue were initially incorrect. Since the team doesn't feel ready we should delay marking v1.19.x as stable.

@brandond
Copy link
Member Author

brandond commented Nov 7, 2020

Was it 1.19 that we're not comfortable with, or just not ready to call etcd stable yet? I can do either. @cjellick ?

@davidnuzik
Copy link
Contributor

Per our discussion today in Standup, we're okay with marking v1.19.3+k3s2 as stable.

Copy link
Contributor

@davidnuzik davidnuzik left a comment

Choose a reason for hiding this comment

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

LGTM

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.

2 participants