For the go1.23rc1 release announcement, we want to: - Highlight the version of gopls required to use new language features (in this case, this will be gopls@v0.16.0 or gopls@v0.16.0-pre.1). - Ask users to opt-in to telemetry to help improve our releases.
@dmitshur suggests that the easiest way to do this may be to modify the announcement template at https://cs.opensource.google/go/x/build/+/master:internal/task/template/announce-rc.md;drc=59c99abb1cb61040972a82e0e4ba4f61a95ac34e
For this release, we could guard these additions with {{if eq .Version "go1.23rc1"}}, but in fact we may want to include both of these features in all future release candidate announcements. It seems like it may always be worthwhile to inform users which gopls version is required to work with new language features, and to ask them to enable telemetry so that we can collect more information about the release candidate.
CC @dmitshur @joedian @rsc
Comment From: findleyr
If we do release gopls@v0.16.0 before the rc1, we may not need to mention gopls, since many editors auto-update. However, we do regularly see users confused because they forgot to reinstall their tools. We could perhaps suggest reinstalling tools as part of the release announcement :thinking:.
Comment From: gopherbot
Change https://go.dev/cl/592199 mentions this issue: internal/task: suggest enabling telemetry in RC announcements
Comment From: findleyr
I'm not yet closing this issue with the above CL, because depending on whether we land gopls@v0.16.0, we may want to also suggest using gopls@v0.16.0-pre.1. If we are able to release gopls prior to the RC, no such addition is necessary, since most users are auto-updated to the latest gopls version.
Comment From: dr2chase
This is marked as a release blocker, is open, is not marked okay-after-RC1, and the scheduled cut for 1.23RC1 is roughly 24 hours from now. Where do we stand on this?
Comment From: gopherbot
Change https://go.dev/cl/593055 mentions this issue: internal/task: update the go1.23rc1 announcement to mention gopls
Comment From: gopherbot
Change https://go.dev/cl/593057 mentions this issue: internal/task: unify handling of regular and fenced code blocks
Comment From: gopherbot
Change https://go.dev/cl/593679 mentions this issue: internal/task/template: remove special gopls instructions for go1.23rc1