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

wiki: Go-Release-Cycle has an out of date statement on backporting policy #37097

Closed
dmitshur opened this issue Feb 7, 2020 · 6 comments
Closed
Labels
Documentation FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@dmitshur
Copy link
Contributor

dmitshur commented Feb 7, 2020

There is a statement in the Release Maintenance section of the Go Release Cycle wiki page that is out of date:

Minor releases to address non-security problems for Go 1.x stop once Go 1.x+1 is released.

I plan to edit the page to make it say:

Minor releases to address non-security problems for Go 1.x stop once Go 1.x+2 is released.

This is because we've accepted a backport policy clarification in proposal #34536, which makes it clear that the last two releases are supported equally.

(Filing this issue before making the change, as documented in the first paragraph of that wiki page.)

/cc @rsc @andybons @cagedmantis @toothrot

@dmitshur dmitshur added Documentation NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. labels Feb 7, 2020
@dmitshur dmitshur added this to the Unreleased milestone Feb 7, 2020
@dmitshur
Copy link
Contributor Author

dmitshur commented Feb 7, 2020

Note that the very next sentence in that section talks about security problems being fixed in the last two releases:

Minor releases to address non-security problems for Go 1.x stop once Go 1.x+1 is released.

Minor releases to address security problems for Go 1.x stop once Go 1.x+2 is released. For more about security updates, see the security policy.

So there is also an option to combine the two into something like:

Minor releases to address non-security and security problems for Go 1.x stop once Go 1.x+2 is released. For more about security updates, see the security policy.

@dmitshur
Copy link
Contributor Author

dmitshur commented May 7, 2020

This issue has received 2 thumbs up from release team members, and no concerns have been raised. It's small and obvious fix, so it doesn't seem like more discussion is needed.

I'll proceed with making the change.

@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. labels May 7, 2020
@dmitshur dmitshur self-assigned this May 8, 2020
@dmitshur
Copy link
Contributor Author

dmitshur commented May 12, 2020

Fixed in wiki commit e05fa49b.

@mvdan
Copy link
Member

mvdan commented Jan 13, 2021

I think the text is now repetitive and confusing:

Minor releases to address non-security problems for Go 1.x stop once Go 1.x+2 is released.
Minor releases to address security problems for Go 1.x stop once Go 1.x+2 is released.

Why have two almost exact sentences? I had to read them twice to make sure the only difference was security vs non-security. They should be merged, in my opinion.

@dmitshur
Copy link
Contributor Author

@mvdan Do you think the suggested combined phrasing in #37097 (comment) would work well?

@mvdan
Copy link
Member

mvdan commented Jan 13, 2021

Sure. Though saying "non-security and security" feels a bit weird, like saying "all important and non-important bugs" when one could just say "all bugs".

@golang golang locked and limited conversation to collaborators Jan 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Documentation FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

3 participants