-
Notifications
You must be signed in to change notification settings - Fork 18k
spec: update unification rules [1.21 backport] #62207
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
Comments
@griesemer Sorry, I just noticed this issue in the Go1.21.1 milestone now. It was missed during cherry pick review earlier because it didn't have the usual CherryPickCandidate label and "[1.21 backport]" suffix (see https://go.dev/wiki/MinorReleases). The release branches are have recently been frozen in the preparation for the upcoming minor release. Is it okay for this backport to land for Go 1.21.2 instead, or is it worth adding release-blocking label to make sure this is reviewed for Go 1.21.1? Thanks. |
Yes that's fine. I haven't even gotten to this yet and it won't really impact anyone for real. There's no urgency. (The changes are in the Appendix section of the spec.) |
Approved. This is documentation only. |
Hi @griesemer looking at the schedule for Go 1.21.2 I think we are supposed to have all cherry-picks done by this Tues in order to freeze the release branch Wed and pre-announce on Thu. Will the fix for this bug make the release do you think, or should we bump to 1.21.3? Thanks. |
Late here, but what is the status here? |
If we usually don't backport spec changes, I think we can close this. Thanks. |
Reminder issue to update unification rules per fix for #62157.
The text was updated successfully, but these errors were encountered: