Skip to content
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

all: write release blog post #27155

Closed
andybons opened this issue Aug 22, 2018 · 8 comments
Closed

all: write release blog post #27155

andybons opened this issue Aug 22, 2018 · 8 comments
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. recurring Issues that should never be closed, but moved to the next milestone once fixed in the current one. release-blocker
Milestone

Comments

@andybons
Copy link
Member

Move to the next major release milestone once this is completed.

@andybons andybons added NeedsFix The path to resolution is known, but the work has not been done. release-blocker labels Aug 22, 2018
@andybons andybons added this to the Go1.11 milestone Aug 22, 2018
@andybons andybons self-assigned this Aug 22, 2018
@andybons andybons modified the milestones: Go1.11, Go1.12 Aug 25, 2018
@ianlancetaylor ianlancetaylor changed the title Write release blog Post all: write release blog Post Nov 28, 2018
@ianlancetaylor ianlancetaylor changed the title all: write release blog Post all: write release blog post Nov 28, 2018
@andybons andybons modified the milestones: Go1.12, Go1.13 Feb 25, 2019
@jba

This comment has been minimized.

@gopherbot
Copy link

Change https://golang.org/cl/192741 mentions this issue: content: add go1.13.article

@andybons andybons modified the milestones: Go1.13, Go1.14 Sep 2, 2019
gopherbot pushed a commit to golang/blog that referenced this issue Sep 3, 2019
Updates golang/go#27155

Change-Id: I54310852ace172ffa0d900f20402bf364bbb7034
Reviewed-on: https://go-review.googlesource.com/c/blog/+/192741
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
@andybons andybons removed their assignment Sep 18, 2019
@gopherbot
Copy link

Change https://golang.org/cl/220649 mentions this issue: content: add go1.14.article

@cagedmantis

This comment has been minimized.

@cagedmantis cagedmantis modified the milestones: Go1.14, Go1.15 Feb 25, 2020
gopherbot pushed a commit to golang/blog that referenced this issue Feb 25, 2020
Updates golang/go#27155

Change-Id: I54e45d5ebaa6955e8cfb52e5ce174d3d372035d3
Reviewed-on: https://go-review.googlesource.com/c/blog/+/220649
Run-TryBot: Alexander Rakoczy <alex@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Toshihiro Shiino <shiino.toshihiro@gmail.com>
Reviewed-by: Carlos Amedee <carlos@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
@dmitshur dmitshur added the okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 label May 14, 2020
@toothrot toothrot removed the okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 label Jun 10, 2020
@andybons andybons added the recurring Issues that should never be closed, but moved to the next milestone once fixed in the current one. label Jul 30, 2020
@gopherbot
Copy link

Change https://golang.org/cl/247406 mentions this issue: content: add go1.15.article

gopherbot pushed a commit to golang/blog that referenced this issue Aug 11, 2020
For golang/go#27155

Change-Id: I6c0a2a7b9293a39393192920c3625b6f09d77e0a
Reviewed-on: https://go-review.googlesource.com/c/blog/+/247406
Reviewed-by: Carlos Amedee <carlos@golang.org>
@dmitshur dmitshur added the okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 label Nov 5, 2020
@toothrot toothrot removed the okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 label Dec 17, 2020
@toothrot toothrot added this to Planned in Go Release Team Feb 2, 2021
@dmitshur dmitshur self-assigned this Feb 9, 2021
@dmitshur
Copy link
Contributor

@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.

Go Release Team automation moved this from Planned to Done Feb 16, 2021
@gopherbot
Copy link

Change https://golang.org/cl/292689 mentions this issue: content: add go1.16.article

gopherbot pushed a commit to golang/blog that referenced this issue Feb 16, 2021
For golang/go#44292.
Updates golang/go#27155.

Co-authored-by: Matt Pearring <pearring@users.noreply.github.com>
Change-Id: I6e0d6731d5848f81fce7e77cbb068174462c0e4e
Reviewed-on: https://go-review.googlesource.com/c/blog/+/292689
Trust: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
gopherbot pushed a commit to golang/website that referenced this issue May 26, 2021
Updates golang/go#27155

Change-Id: I54310852ace172ffa0d900f20402bf364bbb7034
Reviewed-on: https://go-review.googlesource.com/c/blog/+/192741
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
X-Blog-Commit: 1792453c68dc55557c18391a89de33f74beab06a
gopherbot pushed a commit to golang/website that referenced this issue May 26, 2021
Updates golang/go#27155

Change-Id: I54e45d5ebaa6955e8cfb52e5ce174d3d372035d3
Reviewed-on: https://go-review.googlesource.com/c/blog/+/220649
Run-TryBot: Alexander Rakoczy <alex@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Toshihiro Shiino <shiino.toshihiro@gmail.com>
Reviewed-by: Carlos Amedee <carlos@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
X-Blog-Commit: 60e8775bc94bc93d02b5fe03b57bcb265ff69290
gopherbot pushed a commit to golang/website that referenced this issue May 26, 2021
For golang/go#27155

Change-Id: I6c0a2a7b9293a39393192920c3625b6f09d77e0a
Reviewed-on: https://go-review.googlesource.com/c/blog/+/247406
Reviewed-by: Carlos Amedee <carlos@golang.org>
X-Blog-Commit: 3841cf6a3ea0effaf63edb48a2cc0973c56ce756
gopherbot pushed a commit to golang/website that referenced this issue May 26, 2021
For golang/go#44292.
Updates golang/go#27155.

Co-authored-by: Matt Pearring <pearring@users.noreply.github.com>
Change-Id: I6e0d6731d5848f81fce7e77cbb068174462c0e4e
Reviewed-on: https://go-review.googlesource.com/c/blog/+/292689
Trust: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
X-Blog-Commit: c4aa98e750f4c42d7ff9b909ac5e5d83d0b92769
@gopherbot
Copy link

Change https://golang.org/cl/342589 mentions this issue: blog: add go1.17.article

gopherbot pushed a commit to golang/website that referenced this issue Aug 16, 2021
For golang/go#47719
Updates golang/go#27155

Change-Id: Ied7ea9213bd318eae7bb327a5fc29c3bc9cc812a
Co-authored-by: Matt Pearring <pearring@users.noreply.github.com>
Reviewed-on: https://go-review.googlesource.com/c/website/+/342589
Trust: Alexander Rakoczy <alex@golang.org>
Run-TryBot: Alexander Rakoczy <alex@golang.org>
Reviewed-by: Michael Knyszek <mknyszek@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Website-Publish: DO NOT USE <dmitshur@google.com>
passionSeven added a commit to passionSeven/website that referenced this issue Oct 18, 2022
Updates golang/go#27155

Change-Id: I54310852ace172ffa0d900f20402bf364bbb7034
Reviewed-on: https://go-review.googlesource.com/c/blog/+/192741
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
X-Blog-Commit: 1792453c68dc55557c18391a89de33f74beab06a
passionSeven added a commit to passionSeven/website that referenced this issue Oct 18, 2022
Updates golang/go#27155

Change-Id: I54e45d5ebaa6955e8cfb52e5ce174d3d372035d3
Reviewed-on: https://go-review.googlesource.com/c/blog/+/220649
Run-TryBot: Alexander Rakoczy <alex@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Toshihiro Shiino <shiino.toshihiro@gmail.com>
Reviewed-by: Carlos Amedee <carlos@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
X-Blog-Commit: 60e8775bc94bc93d02b5fe03b57bcb265ff69290
passionSeven added a commit to passionSeven/website that referenced this issue Oct 18, 2022
For golang/go#27155

Change-Id: I6c0a2a7b9293a39393192920c3625b6f09d77e0a
Reviewed-on: https://go-review.googlesource.com/c/blog/+/247406
Reviewed-by: Carlos Amedee <carlos@golang.org>
X-Blog-Commit: 3841cf6a3ea0effaf63edb48a2cc0973c56ce756
passionSeven added a commit to passionSeven/website that referenced this issue Oct 18, 2022
For golang/go#44292.
Updates golang/go#27155.

Co-authored-by: Matt Pearring <pearring@users.noreply.github.com>
Change-Id: I6e0d6731d5848f81fce7e77cbb068174462c0e4e
Reviewed-on: https://go-review.googlesource.com/c/blog/+/292689
Trust: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
X-Blog-Commit: c4aa98e750f4c42d7ff9b909ac5e5d83d0b92769
passionSeven added a commit to passionSeven/website that referenced this issue Oct 18, 2022
For golang/go#47719
Updates golang/go#27155

Change-Id: Ied7ea9213bd318eae7bb327a5fc29c3bc9cc812a
Co-authored-by: Matt Pearring <pearring@users.noreply.github.com>
Reviewed-on: https://go-review.googlesource.com/c/website/+/342589
Trust: Alexander Rakoczy <alex@golang.org>
Run-TryBot: Alexander Rakoczy <alex@golang.org>
Reviewed-by: Michael Knyszek <mknyszek@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Website-Publish: DO NOT USE <dmitshur@google.com>
@golang golang locked and limited conversation to collaborators Jun 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. recurring Issues that should never be closed, but moved to the next milestone once fixed in the current one. release-blocker
Projects
Archived in project
Development

No branches or pull requests

6 participants