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: MinorReleases has an out of date statement on backporting policy #40206

Closed
dmitshur opened this issue Jul 14, 2020 · 3 comments
Closed
Labels
Documentation Issues describing a change to documentation. FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@dmitshur
Copy link
Contributor

The https://golang.org/wiki/MinorReleases page currently still says:

"Use a more recent stable version" is a valid workaround, so very few fixes will be backported to both previous issues.

That statement isn't true per discussion in #34536. We should either update it or remove it. If it's not already said elsewhere on the page, we should likely replace it with something similar to what's written in #34536 (comment).

/cc @ianlancetaylor @cagedmantis @toothrot @andybons

@dmitshur dmitshur added Documentation Issues describing a change to documentation. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Jul 14, 2020
@mdempsky
Copy link
Contributor

Example confusion: For #40917, I read that sentence and understood that if we backport the fix to Go 1.15, a "valid workaround" would be to tell users "use a more recent stable version" (e.g., Go 1.15.1).

That seems to contradict #34536 (comment), which says it should be ported to both Go 1.14+1.15, as the regression was introduced in 1.14.

@dmitshur
Copy link
Contributor Author

dmitshur commented Aug 21, 2020

I'm going to remove the incorrect statement for now, but keep this issue open because I think we should add something that makes the policy as described in #34536 (comment) clear for people who read only https://golang.org/wiki/MinorReleases.

Edit: Done in wiki commit 32013d6f.

@dmitshur dmitshur added this to the Unreleased milestone Aug 22, 2020
@dmitshur dmitshur changed the title wiki: MinorReleases has an out of date statement on backporting policy wiki: MinorReleases doesn't make it clear that last two releases are supported equally Mar 8, 2021
@dmitshur
Copy link
Contributor Author

dmitshur commented Mar 8, 2021

Hmm, I think it'll be more clear to keep this issue about the clearly incorrect statement as mentioned in the original issue comment (which has been fixed, see comment above), and reopen #34536 to finish documenting the policy on the MinorReleases wiki page.

@dmitshur dmitshur changed the title wiki: MinorReleases doesn't make it clear that last two releases are supported equally wiki: MinorReleases has an out of date statement on backporting policy Mar 8, 2021
@dmitshur dmitshur self-assigned this Mar 8, 2021
@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Mar 8, 2021
@dmitshur dmitshur closed this as completed Mar 8, 2021
@golang golang locked and limited conversation to collaborators Mar 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Documentation Issues describing a change to 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