-
Notifications
You must be signed in to change notification settings - Fork 18k
all: write release blog post #27155
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
This comment has been minimized.
This comment has been minimized.
Change https://golang.org/cl/192741 mentions this issue: |
Updates golang/go#27155 Change-Id: I54310852ace172ffa0d900f20402bf364bbb7034 Reviewed-on: https://go-review.googlesource.com/c/blog/+/192741 Reviewed-by: Dmitri Shuralyov <[email protected]>
Change https://golang.org/cl/220649 mentions this issue: |
This comment has been minimized.
This comment has been minimized.
Updates golang/go#27155 Change-Id: I54e45d5ebaa6955e8cfb52e5ce174d3d372035d3 Reviewed-on: https://go-review.googlesource.com/c/blog/+/220649 Run-TryBot: Alexander Rakoczy <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Toshihiro Shiino <[email protected]> Reviewed-by: Carlos Amedee <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>
Change https://golang.org/cl/247406 mentions this issue: |
For golang/go#27155 Change-Id: I6c0a2a7b9293a39393192920c3625b6f09d77e0a Reviewed-on: https://go-review.googlesource.com/c/blog/+/247406 Reviewed-by: Carlos Amedee <[email protected]>
@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. |
Change https://golang.org/cl/292689 mentions this issue: |
For golang/go#44292. Updates golang/go#27155. Co-authored-by: Matt Pearring <[email protected]> Change-Id: I6e0d6731d5848f81fce7e77cbb068174462c0e4e Reviewed-on: https://go-review.googlesource.com/c/blog/+/292689 Trust: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>
Updates golang/go#27155 Change-Id: I54310852ace172ffa0d900f20402bf364bbb7034 Reviewed-on: https://go-review.googlesource.com/c/blog/+/192741 Reviewed-by: Dmitri Shuralyov <[email protected]> X-Blog-Commit: 1792453c68dc55557c18391a89de33f74beab06a
Updates golang/go#27155 Change-Id: I54e45d5ebaa6955e8cfb52e5ce174d3d372035d3 Reviewed-on: https://go-review.googlesource.com/c/blog/+/220649 Run-TryBot: Alexander Rakoczy <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Toshihiro Shiino <[email protected]> Reviewed-by: Carlos Amedee <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> X-Blog-Commit: 60e8775bc94bc93d02b5fe03b57bcb265ff69290
For golang/go#27155 Change-Id: I6c0a2a7b9293a39393192920c3625b6f09d77e0a Reviewed-on: https://go-review.googlesource.com/c/blog/+/247406 Reviewed-by: Carlos Amedee <[email protected]> X-Blog-Commit: 3841cf6a3ea0effaf63edb48a2cc0973c56ce756
For golang/go#44292. Updates golang/go#27155. Co-authored-by: Matt Pearring <[email protected]> Change-Id: I6e0d6731d5848f81fce7e77cbb068174462c0e4e Reviewed-on: https://go-review.googlesource.com/c/blog/+/292689 Trust: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> X-Blog-Commit: c4aa98e750f4c42d7ff9b909ac5e5d83d0b92769
Change https://golang.org/cl/342589 mentions this issue: |
For golang/go#47719 Updates golang/go#27155 Change-Id: Ied7ea9213bd318eae7bb327a5fc29c3bc9cc812a Co-authored-by: Matt Pearring <[email protected]> Reviewed-on: https://go-review.googlesource.com/c/website/+/342589 Trust: Alexander Rakoczy <[email protected]> Run-TryBot: Alexander Rakoczy <[email protected]> Reviewed-by: Michael Knyszek <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Website-Publish: DO NOT USE <[email protected]>
Updates golang/go#27155 Change-Id: I54310852ace172ffa0d900f20402bf364bbb7034 Reviewed-on: https://go-review.googlesource.com/c/blog/+/192741 Reviewed-by: Dmitri Shuralyov <[email protected]> X-Blog-Commit: 1792453c68dc55557c18391a89de33f74beab06a
Updates golang/go#27155 Change-Id: I54e45d5ebaa6955e8cfb52e5ce174d3d372035d3 Reviewed-on: https://go-review.googlesource.com/c/blog/+/220649 Run-TryBot: Alexander Rakoczy <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Toshihiro Shiino <[email protected]> Reviewed-by: Carlos Amedee <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> X-Blog-Commit: 60e8775bc94bc93d02b5fe03b57bcb265ff69290
For golang/go#27155 Change-Id: I6c0a2a7b9293a39393192920c3625b6f09d77e0a Reviewed-on: https://go-review.googlesource.com/c/blog/+/247406 Reviewed-by: Carlos Amedee <[email protected]> X-Blog-Commit: 3841cf6a3ea0effaf63edb48a2cc0973c56ce756
For golang/go#44292. Updates golang/go#27155. Co-authored-by: Matt Pearring <[email protected]> Change-Id: I6e0d6731d5848f81fce7e77cbb068174462c0e4e Reviewed-on: https://go-review.googlesource.com/c/blog/+/292689 Trust: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> X-Blog-Commit: c4aa98e750f4c42d7ff9b909ac5e5d83d0b92769
For golang/go#47719 Updates golang/go#27155 Change-Id: Ied7ea9213bd318eae7bb327a5fc29c3bc9cc812a Co-authored-by: Matt Pearring <[email protected]> Reviewed-on: https://go-review.googlesource.com/c/website/+/342589 Trust: Alexander Rakoczy <[email protected]> Run-TryBot: Alexander Rakoczy <[email protected]> Reviewed-by: Michael Knyszek <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Website-Publish: DO NOT USE <[email protected]>
Move to the next major release milestone once this is completed.
The text was updated successfully, but these errors were encountered: