all: reopen tree for Go 1.24 development

[cagedmantis]

Current Tree Status: Tree is open for Go 1.24 development (golang-dev announcement)

This is a tracking issue for the upcoming task of reopening the tree for Go 1.24 development. (It's created a little early to create room for planning early CLs/branches to land during tree reopening.) The estimated date for the tree reopening is mid July 2024.

As usual, the tree will initially be open to changes that must land early:

• Bump internal/goversion.Version to 24—this should be the very first CL to be submitted as it marks the start of master branch representing Go 1.24 (rather than Go 1.23). (Example CL.)
  • internal/goversion: increment Version at start of cycle #40705
  • Done in CL 600176.
• Initialize doc/next for the Go 1.24 cycle. (See "For the release team" in doc/README.)
  • Done in CL 600177.
• Submit CLs that are ready and marked AutoSubmit+1, but blocked on wait-release (query).
  • There were about 9 such CLs; they're now submitted.
• Submit CLs that are ready and associated with issues labelled as early-in-cycle (query).
  • runtime: remove VZEROUPPER patch once Darwin <10.15.6 is not supported #41152 (CL 560955)
• (Anything else that is missing but should be added here, edit or comment below.)
• Finally, open the tree for all general Go 1.24 changes.

CC @golang/release.

[mvdan]

When you post tree reopening issues like this one, could you please include when you expect it to happen? Given https://go.dev/wiki/Go-Release-Cycle, I would expect mid July, but that might not be obvious to everyone.

[cagedmantis]

@mvdan That sounds perfectly reasonable. Thanks for suggesting it.

[dmitshur]

We've reached the time to reopen. I'll be starting on this soon. So far it seems there aren't any large changes that need special treatment; please comment if we missed something that should land early in a specific order to reduce merge conflicts.

[cuonglm]

We've reached the time to reopen. I'll be starting on this soon. So far it seems there aren't any large changes that need special treatment; please comment if we missed something that should land early in a specific order to reduce merge conflicts.

Is fix for 1.23 needs to be backport?

For example, CL https://go.dev/cl/599675 is land after rc2, but it's for 1.23 release.

[dmitshur]

@cuonglm We'll soon merge everything on the main branch, up to but not including the upcoming "internal/goversion: update Version to 1.24" CL, to release-branch.go1.23. Since CL 599675 is already submitted, no need for action on your side. But in the near future after the goversion CL lands, if something is intended for 1.23 and permitted by freeze policy it will indeed need to be cherry-picked to release-branch.go1.23 individually. See https://go.dev/s/release#july--january-week-3-work-on-the-next-release-begins for details.

[gopherbot]

Change https://go.dev/cl/600176 mentions this issue: internal/goversion: update Version to 1.24

[gopherbot]

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

[dmitshur]

There were about 7 9 CLs that were already approved and marked AutoSubmit+1, but blocked on wait-release. They're now in. I'll wait to see the results on the post-submit dashboard and follow up before proceeding with the rest of the steps in the tree re-opening sequence.

[cuonglm]

@dmitshur CL https://go-review.googlesource.com/c/go/+/560955 could be land in for early in cycle, too.

[dmitshur]

The tree is now open. See announcement on golang-dev. Thanks.

(I'll unpin this issue after some time passes.)

[thanm]

At what point will we change the go.mod version line to 1.24? Not sure if this falls into the realm of this issue, or if it is being tracked elsewhere. Thanks.

[dmitshur]

@thanm That generally happens as part of issue #36905 which is early-in-cycle and we'll get to soon. It's fine to do it separately even sooner if needed.