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

Open
dmitshur opened this issue Jul 14, 2020 · 2 comments
Open

wiki: MinorReleases has an out of date statement on backporting policy #40206

dmitshur opened this issue Jul 14, 2020 · 2 comments

Comments

@dmitshur
Copy link
Member

@dmitshur dmitshur commented Jul 14, 2020

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

@mdempsky
Copy link
Member

@mdempsky mdempsky commented Aug 21, 2020

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
Member Author

@dmitshur 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.