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 release info in README.md #293

Merged
merged 1 commit into from
Apr 25, 2023
Merged

Conversation

rmweir
Copy link
Contributor

@rmweir rmweir commented Apr 14, 2023

No description provided.

README.md Outdated
Wrangler releases use [semantic versioning](https://semver.org/). Patch releases occur on the latest minor release as well as on older minor releases being actively used in supported versions of [Rancher](http://github.com/rancher/rancher). That currently includes:
Wrangler releases use [semantic versioning](https://semver.org/). New major releases are created for breaking changes, new minor releases are created for features, and patches are added for everything else.

The newest Major.Minor.x release and any releases being used by a [supported version of rancher](https://www.suse.com/lifecycle/#rancher) will be maintained. The newest major will receive minor releases, along with patch releases on its most up to date minor release. Older Major.Minor.x releases still in use by rancher will receive security patches at minimum. Consequently, there will be 1-3 maintained releases of the form Major.Minor.x at a time. Currently maintained versions:
Copy link
Contributor

Choose a reason for hiding this comment

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

and any releases being used by a supported version of rancher

This could cause confusion. If 2.6 jumps from 2.0 to 3.0, would we still support 2.0 ? Users could read it that way, but I don't think we would.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

How about any releases being used by the latest patch version of a supported rancher release?

Copy link
Contributor

Choose a reason for hiding this comment

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

I would tweak that a little..

... any releases being used by the most recent patch version of a supported rancher version will be maintained.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Used Matt's.

README.md Outdated Show resolved Hide resolved
README.md Outdated
Wrangler releases use [semantic versioning](https://semver.org/). Patch releases occur on the latest minor release as well as on older minor releases being actively used in supported versions of [Rancher](http://github.com/rancher/rancher). That currently includes:
Wrangler releases use [semantic versioning](https://semver.org/). New major releases are created for breaking changes, new minor releases are created for features, and patches are added for everything else.

The newest Major.Minor.x release and any releases being used by a [supported version of rancher](https://www.suse.com/lifecycle/#rancher) will be maintained. The newest major will receive minor releases, along with patch releases on its most up to date minor release. Older Major.Minor.x releases still in use by rancher will receive security patches at minimum. Consequently, there will be 1-3 maintained releases of the form Major.Minor.x at a time. Currently maintained versions:
Copy link
Contributor

Choose a reason for hiding this comment

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

I would tweak that a little..

... any releases being used by the most recent patch version of a supported rancher version will be maintained.

@mattfarina mattfarina merged commit 39a4707 into rancher:master Apr 25, 2023
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