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

doc: write release notes for Go 1.23 #65614

Open
dmitshur opened this issue Feb 8, 2024 · 4 comments
Open

doc: write release notes for Go 1.23 #65614

dmitshur opened this issue Feb 8, 2024 · 4 comments
Labels
Documentation NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@dmitshur
Copy link
Contributor

dmitshur commented Feb 8, 2024

This is the tracking issue for writing the Go 1.23 Release Notes.

This is the first release to use the improved release note process being implemented in #64169. Also see a corresponding golang-dev thread. (CC @jba.)

Up until the the end of the development cycle (end of May), release note fragments are added inside the doc/next directory in the main Go repo. This is documented in the "For developers" section of doc/README.md:

https://go.googlesource.com/go/+/HEAD/doc/#for-developers

At the end of the development cycle, the doc/next files will be merged into a single go1.23.md file, and all remaining edits will take place in it. This merge will be handled as part of the Go release process.

The previous issue was #61422.

@dmitshur dmitshur added Documentation NeedsFix The path to resolution is known, but the work has not been done. labels Feb 8, 2024
@dmitshur dmitshur added this to the Go1.23 milestone Feb 8, 2024
@gopherbot
Copy link

Change https://go.dev/cl/563856 mentions this issue: doc/go1.23: document macOS requirements

gopherbot pushed a commit that referenced this issue Feb 14, 2024
For #64207.
For #65614.

Change-Id: Ia5365b4090060e0657c255341751d3e67691f836
Reviewed-on: https://go-review.googlesource.com/c/go/+/563856
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Than McIntosh <thanm@google.com>
ezz-no pushed a commit to ezz-no/go-ezzno that referenced this issue Feb 18, 2024
For golang#64207.
For golang#65614.

Change-Id: Ia5365b4090060e0657c255341751d3e67691f836
Reviewed-on: https://go-review.googlesource.com/c/go/+/563856
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Than McIntosh <thanm@google.com>
aimuz added a commit to aimuz/go that referenced this issue Mar 4, 2024
For golang#64707
For golang#65614

Signed-off-by: aimuz <mr.imuz@gmail.com>
@gopherbot
Copy link

Change https://go.dev/cl/568755 mentions this issue: doc/go1.23: document database/sql wrap errors

gopherbot pushed a commit that referenced this issue Mar 4, 2024
For #64707.
For #65614.

Change-Id: Ib07ac67d7652bc7c9e1363f70637938c7bb4bc72
GitHub-Last-Rev: a4d8eca
GitHub-Pull-Request: #66089
Reviewed-on: https://go-review.googlesource.com/c/go/+/568755
Reviewed-by: Ian Lance Taylor <iant@google.com>
Auto-Submit: Ian Lance Taylor <iant@google.com>
Reviewed-by: Michael Knyszek <mknyszek@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
@jfrech
Copy link

jfrech commented Apr 5, 2024

I think 3c78ace's changes are worth mentioning.

@ianlancetaylor
Copy link
Contributor

@jfrech Thanks, but the release notes are for changes that users need to know because they are new or because they will affect the way that programs work. We don't usually mention specific optimizations in the release notes, unless they affect the great majority of Go programs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

4 participants