-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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.24 #68545
Comments
Related Issues and Documentation
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.) |
Change https://go.dev/cl/600177 mentions this issue: |
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 <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Auto-Submit: Dmitri Shuralyov <[email protected]> Reviewed-by: Cherry Mui <[email protected]>
Change https://go.dev/cl/600179 mentions this issue: |
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 <[email protected]> Reviewed-by: Cherry Mui <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Auto-Submit: Dmitri Shuralyov <[email protected]>
Change https://go.dev/cl/600656 mentions this issue: |
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 <[email protected]> Auto-Submit: Dmitri Shuralyov <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>
Change https://go.dev/cl/605615 mentions this issue: |
Change https://go.dev/cl/622015 mentions this issue: |
The minimum Linux kernel version for Go 1.24 is now set to 3.2. Updates #67001 For #68545 Change-Id: I509f09c8ed7f3067af14066cf139008db0cb06ba Reviewed-on: https://go-review.googlesource.com/c/go/+/622015 Auto-Submit: Carlos Amedee <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>
Change https://go.dev/cl/631682 mentions this issue: |
Fixes #60529 Updates #68545 Change-Id: Ica048e4861f4de22deb7f42a1d76eb3151fee986 Reviewed-on: https://go-review.googlesource.com/c/go/+/631682 Auto-Submit: Alan Donovan <[email protected]> Reviewed-by: Robert Findley <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>
Change https://go.dev/cl/635597 mentions this issue: |
Change https://go.dev/cl/635598 mentions this issue: |
Change https://go.dev/cl/635596 mentions this issue: |
FIPS 140 commented out for now, will add a section in a follow-up CL. It's ok for those to come after rc1, also because it's a bit unclear yet what we can assert about the FIPS 140-3 status of the release. Note that none of the changes affect existing programs that don't opt in with the new switches. For golang/go#68545 Change-Id: I9779a0976127e5fdc65b4b8ae3c6c2de4739390b Reviewed-on: https://go-review.googlesource.com/c/website/+/635595 Auto-Submit: Filippo Valsorda <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Reviewed-by: Roland Shoemaker <[email protected]> Reviewed-by: Daniel McCarney <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>
For golang/go#68545 Change-Id: Ie32bb7d09038fb13f738f60d8be99aa6eed69d37 Reviewed-on: https://go-review.googlesource.com/c/website/+/635596 LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Auto-Submit: Filippo Valsorda <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Reviewed-by: Sam Thanawalla <[email protected]>
Thanks to everybody who have worked diligently to complete this draft of the release notes. |
The Go 1.24 Release Notes draft is complete, and all known TODOs have been resolved. Adding okay-after-rc1. This issue now tracks the remaining post-RC 1 work:
|
For golang/go#68545 Change-Id: Ic994abed61389823e261c4c4e1b66f0502f3466a Reviewed-on: https://go-review.googlesource.com/c/website/+/635597 Reviewed-by: Dmitri Shuralyov <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Auto-Submit: Filippo Valsorda <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Reviewed-by: Carlos Amedee <[email protected]>
I struggled to map the old ones to the behavior described in golang/go#50603: a pseudo-version will be generated even if a VCS tag is available, but is not the latest commit. Also, a link to BuildInfo.Main feels useful. For golang/go#68545 Change-Id: Id2642c94a18e22ac56439728f20f01bf87d14a70 Reviewed-on: https://go-review.googlesource.com/c/website/+/635598 Reviewed-by: Sam Thanawalla <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Auto-Submit: Sam Thanawalla <[email protected]> Auto-Submit: Filippo Valsorda <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Reviewed-by: Michael Matloob <[email protected]>
Change https://go.dev/cl/636519 mentions this issue: |
The objdump tool now supports dissassembly on riscv64, loong64, and s390x. Updates golang/go#15255, golang/go#36738. For golang/go#68545. Change-Id: I5e913eb27383f42777baac1cd8436a5c6eb629fd Reviewed-on: https://go-review.googlesource.com/c/website/+/636519 LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>
Change https://go.dev/cl/638296 mentions this issue: |
It's a common misperception that -u is needed more often than it is, perhaps in part due to muscle memory from the GOPATH days. The current release notes suggest that 'go get -u tool' will upgrade all of the current module's tools, but it does more than that -- it will also upgrade all of the direct and indirect non-test dependencies of those tools too. The simplest fix is probably just to remove the -u from this section of the release notes. There are various other details that could be covered, like the -u or -t flags, or that 'go get tool' is a shorthand for 'go get tool@upgrade', but maybe this is sufficient. Updates golang/go#48429 Updates golang/go#68545 Change-Id: I31eeb96dae996a7ffde24d9bae6788d6889e2044 Reviewed-on: https://go-review.googlesource.com/c/website/+/638296 Reviewed-by: David Chase <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Auto-Submit: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Conrad Irwin <[email protected]>
Change https://go.dev/cl/638296 reads
Using
Does not show anything. Yet
does execute. Is anything missing from the docs regarding |
@andig The
In this case, the https://go.dev/ref/mod#go-get section of the Go module reference is where the |
The release notes still have TODO comments
which are not addressed. Currently there is no mentioning of FIPS 140 (or fips140) in the release notes. @FiloSottile @rolandshoemaker @rsc could you help write this? Thanks! |
Yep, will mail today or early tomorrow. |
Change https://go.dev/cl/647856 mentions this issue: |
Change https://go.dev/cl/647855 mentions this issue: |
Change https://go.dev/cl/647797 mentions this issue: |
The release notes do not contain the full function signature, therefore parameter names don't have context. Describe in words instead. Also, for the bytes package, use "subslice" instead of "substring". Also added some words for clarification, and did minor format changes. For golang/go#68545. Change-Id: Ia691264c75b37be54844567f6c65c12d878a29bc Reviewed-on: https://go-review.googlesource.com/c/website/+/647855 Reviewed-by: Dmitri Shuralyov <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>
One is already included. Others don't need to be included. For golang/go#68545. Change-Id: Iae98ea60894f32906911ef6649c4bb8482e6433c Reviewed-on: https://go-review.googlesource.com/c/website/+/647856 LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>
Change https://go.dev/cl/648498 mentions this issue: |
Start using the GOROOT content from release-branch.go1.24, and add an entry for the Go 1.24.0 release to the release history. Removing the draft notice from the release notes is done in CL 647797. For golang/go#68545. Change-Id: Ib30082d4dcc0afaadcf22ba07e5e5f7e3f4761bc Reviewed-on: https://go-review.googlesource.com/c/website/+/648498 Reviewed-by: Dmitri Shuralyov <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Cherry Mui <[email protected]> Auto-Submit: Dmitri Shuralyov <[email protected]>
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.
A partial list of changes that were known on 2024-11-26 to need to be added the release notes:
go build
#50603The text was updated successfully, but these errors were encountered: