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.

Sign up for GitHub

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

Jump to bottom

doc: write release notes for Go 1.24 #68545

Open
dmitshur opened this issue Jul 22, 2024 · 5 comments
Open

doc: write release notes for Go 1.24 #68545

dmitshur opened this issue Jul 22, 2024 · 5 comments
Labels
Documentation NeedsFix The path to resolution is known, but the work has not been done. release-blocker
Milestone
Go1.24

Comments

@dmitshur
Copy link
Contributor

dmitshur commented Jul 22, 2024 •
edited
Loading

This is the tracking issue for writing the Go 1.24 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/go1.24.

When the Go 1.24 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. The previous issue was #65614.
@dmitshur dmitshur added Documentation NeedsFix The path to resolution is known, but the work has not been done. release-blocker labels Jul 22, 2024
@dmitshur dmitshur added this to the Go1.24 milestone Jul 22, 2024
@gabyhelp
Copy link

Related Issues and Documentation

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/600177 mentions this issue: doc: initialize next directory for Go 1.24

gopherbot pushed a commit that referenced this issue Jul 22, 2024
@dmitshur @gopherbot
doc: initialize next directory for Go 1.24
e8c5bed 
Following the "For the release team" steps in README:

	cd doc
	cp -R initial/ next
	$EDITOR next/1-intro.md

Dropped '*' from the cp -R command to avoid needing to
create an empty next directory with a separate command.

For #68545.
For #67586.

Change-Id: I25215bc35a043e0f26d4a86ffe66eb3c26348fef
Reviewed-on: https://go-review.googlesource.com/c/go/+/600177
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: Cherry Mui <cherryyz@google.com>
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/600179 mentions this issue: _content/doc: add go1.24.md placeholder

gopherbot pushed a commit to golang/website that referenced this issue Jul 22, 2024
@dmitshur @gopherbot
_content/doc: add go1.24.md placeholder
ed6d739 
Add this file now so that it's possible to preview the latest release
notes draft at https://tip.golang.org/doc/go1.24, and to include that
link in the tracking issue. Based on CL 588057 that did this for 1.23.

For golang/go#68545.

Change-Id: I07f30023d23ec027927f7417ebece4110f221efa
Reviewed-on: https://go-review.googlesource.com/c/website/+/600179
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Cherry Mui <cherryyz@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/600656 mentions this issue: doc/next: use relative link to Go issue

gopherbot pushed a commit that referenced this issue Jul 24, 2024
@dmitshur @gopherbot
doc/next: use relative link to Go issue
792a261 
The Go release notes are served on multiple domains (go.dev,
golang.google.cn, tip.golang.org, localhost:8080 and so on), so links
pointing to the Go website itself need to be relative to work in all
those contexts.

Caught by a test in x/website. The next CL adds the same test to this
repository so these kinds of problems are caught sooner and with less
friction.

For #68545.
Fixes #68575.

Change-Id: I08056b98968c77a1d0ed93b63fccfbe41274ec8f
Reviewed-on: https://go-review.googlesource.com/c/go/+/600656
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/605615 mentions this issue: doc/next: document version stamping for go builds within a Git Repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Documentation NeedsFix The path to resolution is known, but the work has not been done. release-blocker
Projects
None yet
Milestone
Go1.24
Development

No branches or pull requests
3 participants
@dmitshur @gopherbot @gabyhelp