Updates golang/go#27155 Change-Id: I54310852ace172ffa0d900f20402bf364bbb7034 Reviewed-on: https://go-review.googlesource.com/c/blog/+/192741 Reviewed-by: Dmitri Shuralyov <email@example.com>
Updates golang/go#27155 Change-Id: I54e45d5ebaa6955e8cfb52e5ce174d3d372035d3 Reviewed-on: https://go-review.googlesource.com/c/blog/+/220649 Run-TryBot: Alexander Rakoczy <firstname.lastname@example.org> TryBot-Result: Gobot Gobot <email@example.com> Reviewed-by: Ian Lance Taylor <firstname.lastname@example.org> Reviewed-by: Toshihiro Shiino <email@example.com> Reviewed-by: Carlos Amedee <firstname.lastname@example.org> Reviewed-by: Dmitri Shuralyov <email@example.com>
For golang/go#27155 Change-Id: I6c0a2a7b9293a39393192920c3625b6f09d77e0a Reviewed-on: https://go-review.googlesource.com/c/blog/+/247406 Reviewed-by: Carlos Amedee <firstname.lastname@example.org>
@pearring and I have a Go 1.16 blog post draft ready and will be publishing it as part of the Go 1.16 release.
Because this issue is marked as a release-blocker, @golang/release ends up seeing it throughout the 6 month cycle, but it's usually not at all actionable until the last week. We already track the task of starting the blog post draft and publishing it in our release plan, so it won't be missed. (We can and do filter out by the "recurring" label, but other recurring release blocking issues are still more useful to see occasionally.) So, I'm going to close this.
For golang/go#44292. Updates golang/go#27155. Co-authored-by: Matt Pearring <email@example.com> Change-Id: I6e0d6731d5848f81fce7e77cbb068174462c0e4e Reviewed-on: https://go-review.googlesource.com/c/blog/+/292689 Trust: Dmitri Shuralyov <firstname.lastname@example.org> Reviewed-by: Dmitri Shuralyov <email@example.com>