Please help with Go 1.17 release notes

[Dmitri Shuralyov]

Hi gophers,

We've entered the freeze for Go 1.17, and the golang.org/s/release timeline

allows us to issue Go 1.17 Beta 1 on June 1 (less than 4 weeks away now!)

if all release-blocking issues in scope for the beta are resolved by then.

As of this moment, I'm counting 2036 commits¹ since CL 275297 was submitted

when the tree opened for Go 1.17 development. We need everyone's help with

summarizing those improvements by completing the Go 1.17 release notes draft,

and doing so will unblock the Go 1.17 Beta 1 release.

There are currently 44 matches for "TODO" at https://tip.golang.org/doc/go1.17.

We opened small issues for distinct sections that have outstanding TODOs to

help everyone coordinate and use plenty of concurrency:

https://github.com/golang/go/issues?q=is%3Aissue+is%3Aopen+label%3Arelease-blocker+milestone%3AGo1.17+label%3ADocumentation+%22doc%2Fgo1.17%3A%22+-label%3Arecurring

Please help make progress:

• Review any existing CLs (find them at https://go-review.googlesource.com/q/project:go+status:open+doc/go1.17+label:Code-Review%253C%253D1)
• Pick some unassigned issue, and take ownership over its resolution if you can
• If the issue is still in NeedsInvestigation stage, suggest a possible wording to help move it to NeedsFix state
• If the issue is in NeedsFix state, mail a CL if that's all that's left to do

Thank you for all you do to make Go 1.17 an excellent release!

Dmitri

¹ There are merge commits, so the actual number of changes is much higher.

[Manlio Perillo]

On Thursday, May 6, 2021 at 11:34:06 PM UTC+2 dmit...@golang.org wrote:

Hi gophers,

We've entered the freeze for Go 1.17, and the golang.org/s/release timeline

allows us to issue Go 1.17 Beta 1 on June 1 (less than 4 weeks away now!)

if all release-blocking issues in scope for the beta are resolved by then.

As of this moment, I'm counting 2036 commits¹ since CL 275297 was submitted

when the tree opened for Go 1.17 development. We need everyone's help with

summarizing those improvements by completing the Go 1.17 release notes draft,

and doing so will unblock the Go 1.17 Beta 1 release.

Is the change in https://golang.org/cl/288693 worth mentioning in the release note?

Thanks

Manlio 

[Ian Lance Taylor]

In my opinion, no. The release notes aren't a place to note every
improvement. They are to let people know about new functionality and
about changes in behavior that may affect the way that they use Go.
Thanks.

Ian