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
x/website: merge module doc changes as part of Go 1.16 release #44249
Comments
Thanks. If I understand correctly, @jayconrod is planning to submit that CL stack as part of the Go 1.16 release, and we will coordinate the timing as needed. The merge conflict is because it’s a CL in the middle of a stack, I don’t think it’s a problem. The comments will need to be addressed. Also CC @rsc, @stevetraut as FYI. |
Great! Thanks for confirming. I was trying to find documentation for the new |
For Go 1.16, yes, but that isn't a great experience and we'll look about improving it in the future (perhaps with a branch, or something else). CL 291693 goes a long way to reduce the tight coupling between the main repo and x/website, which will give us good options to work with. |
I left a comment on CL 284812, the first unmerged CL in that stack, noting that it's safe to start landing it now. CC @jayconrod. |
Fixed by merging the aforementioned CL stack. |
1.16 introduces a
retract
directive. The new directive is not mentioned in the Go Modules Reference. The CL adding the doc will need to be merged before the 1.16 release (currently has a merge conflict).In 1.16, go install will accepts arguments with version suffixes (
go install pkg@version
). The CL adding the relevant doc will need to be merged before the 1.16 release (currently has a merge conflict, and unresolved comments).Filing an issue just to be sure this is on someone's radar.
cc @dmitshur @bcmills
The text was updated successfully, but these errors were encountered: