-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
doc: write release notes #15810
Comments
Mostly complete but a few TODOs remain for future CLs. For #15810. Change-Id: I81ee19d1088d192cf709a5f7e6b7bcc44ad892ac Reviewed-on: https://go-review.googlesource.com/23379 Reviewed-by: Andrew Gerrand <[email protected]> Run-TryBot: Russ Cox <[email protected]>
Slight change in |
CL https://golang.org/cl/23493 mentions this issue. |
Document new behavior about signal name printing in panics as per CL golang.org/cl/22753. For #15810 Change-Id: I9c677d5dd779b41e82afa25e3c797d8e739600d3 Reviewed-on: https://go-review.googlesource.com/23493 Reviewed-by: Russ Cox <[email protected]>
CL https://golang.org/cl/23488 mentions this issue. |
For #15810. Change-Id: Ib529808f664392feb9b36770f3d3d875fcb54528 Reviewed-on: https://go-review.googlesource.com/23488 Run-TryBot: Russ Cox <[email protected]> Reviewed-by: Rob Pike <[email protected]> TryBot-Result: Gobot Gobot <[email protected]>
https://tip.golang.org/doc/go1.7 still mentions SizedReaderAt and File.Size Also new package net/http/httptrace (https://tip.golang.org/pkg/net/http/httptrace/) is not mentioned. |
Leaving these last few fixes for @adg. Thanks for catching those @kostya-sh. For that matter api/next.txt needs updating too. |
@adg, in addition to what @kostya-sh said, see @dsnet's comment above. |
Updates #15810 Change-Id: I37f14a0ed1f5ac24ea2169a7e65c0469bfddd928 Reviewed-on: https://go-review.googlesource.com/23559 Reviewed-by: Michael McGreevy <[email protected]> Reviewed-by: Andrew Gerrand <[email protected]>
I believe the docs are in good shape for the beta now. |
CL https://golang.org/cl/23614 mentions this issue. |
Implementation changed in https://golang.org/cl/23612. Updates #15810 Change-Id: I8fff9e3aa3e54162546bb9ec1cc2ebba2b6d9fed Reviewed-on: https://go-review.googlesource.com/23614 Reviewed-by: Ian Lance Taylor <[email protected]>
Still no mention of net/http/httptrace |
@tombergan I'm on it. |
Updates #15810 Change-Id: I689e18409a88c9e8941aa2e98f472c331efd455e Reviewed-on: https://go-review.googlesource.com/23674 Reviewed-by: Ian Lance Taylor <[email protected]>
CL https://golang.org/cl/24731 mentions this issue. |
Document that the http.Server is now stricter about rejecting requests with invalid HTTP versions, and also that it rejects plaintext HTTP/2 requests, except for `PRI * HTTP/2.0` upgrade requests. The relevant CL is https://golang.org/cl/24505. Updates #15810. Change-Id: Ibbace23e001b5e2eee053bd341de50f9b6d3fde8 Reviewed-on: https://go-review.googlesource.com/24731 Reviewed-by: Brad Fitzpatrick <[email protected]>
Hello! not sure if this is separate issue or not. My apologizes on nitpicking a sentence but this one confused me. In the "Minor changes to the library" is this
Maybe a simpler statement such as "There are many performance optimizations throughout the package." would be more clear. Looking forward to 1.7 thanks! n |
Seems done enough for me. I'd just fix @client9's thing and remove the DRAFT heading. |
CL https://golang.org/cl/25591 mentions this issue. |
Updates #15810. Change-Id: Ifa7d2fd7fbfe58dff8541b18a11f007a5ff5818a Reviewed-on: https://go-review.googlesource.com/25591 Reviewed-by: Brad Fitzpatrick <[email protected]>
CL https://golang.org/cl/25592 mentions this issue. |
Updates golang#15810. Change-Id: Ifa7d2fd7fbfe58dff8541b18a11f007a5ff5818a Reviewed-on: https://go-review.googlesource.com/25591 Reviewed-by: Brad Fitzpatrick <[email protected]>
Updates golang#15810. Change-Id: Ifa7d2fd7fbfe58dff8541b18a11f007a5ff5818a Reviewed-on: https://go-review.googlesource.com/25591 Reviewed-by: Brad Fitzpatrick <[email protected]>
Go 1.7 beta needs proper release notes. They are in progress.
The text was updated successfully, but these errors were encountered: