Closed bradfitz closed 7 years ago
CL https://golang.org/cl/45011 mentions this issue.
CL https://golang.org/cl/45012 mentions this issue.
CL https://golang.org/cl/45014 mentions this issue.
CL https://golang.org/cl/45050 mentions this issue.
CL https://golang.org/cl/45051 mentions this issue.
CL https://golang.org/cl/45091 mentions this issue.
CL https://golang.org/cl/45116 mentions this issue.
CL https://golang.org/cl/45118 mentions this issue.
CL https://golang.org/cl/45550 mentions this issue.
CL https://golang.org/cl/45613 mentions this issue.
CL https://golang.org/cl/45730 mentions this issue.
CL https://golang.org/cl/45780 mentions this issue.
CL https://golang.org/cl/45810 mentions this issue.
CL https://golang.org/cl/45811 mentions this issue.
CL https://golang.org/cl/45910 mentions this issue.
CL https://golang.org/cl/46717 mentions this issue.
Relnotes usually have a gccgo
subsection in the Tools
section explaining how's gccgo
doing and what version to expect in the next release (e.g. http://tip.golang.org/doc/go1.8#gccgo, http://tip.golang.org/doc/go1.7#gccgo, http://tip.golang.org/doc/go1.6#gccgo). Currently missing from the 1.9 relnotes.
CL https://golang.org/cl/47034 mentions this issue.
CL https://golang.org/cl/47092 mentions this issue.
CL https://golang.org/cl/47331 mentions this issue.
CL https://golang.org/cl/47551 mentions this issue.
CL https://golang.org/cl/47610 mentions this issue.
Seems done. No changes from final review CL (CL 47610).
https://github.com/golang/go/issues/21289 - crypto/x509 change I believe is missing, though it's probably too late now...
Change https://golang.org/cl/53370 mentions this issue: doc: mention handling of moved GOROOT in 1.9 release notes
Write go1.9.html.
Start of a tool was just submitted in https://golang.org/cl/44814 :