all: reopen tree for Go 1.25 development

[dmitshur]

Current Tree Status: Release freeze for Go 1.24 (see golang-dev announcement)

Now that we've entered the freeze for Go 1.24, we will eventually need to reopen the tree for Go 1.25 development. This is the tracking issue for that reopening, created early so that it's available for planning. The tree reopening is estimated to begin around week 3 of January 2025 (see https://go.dev/s/release#timeline), exact timing depends on how well the Go 1.24 release preparations are going.

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

• Bump internal/goversion.Version to 25—this should be the very first CL to be submitted as it marks the start of main branch representing Go 1.25 (rather than Go 1.24). (Example CL.)
  • internal/goversion: increment Version at start of cycle #40705
• Initialize doc/next for the Go 1.25 cycle. (See "For the release team" in doc/README.)
• Submit CLs that are ready and marked AutoSubmit+1, but blocked on wait-release (query).
• Look over issues labelled as early-in-cycle for anything needs to land very early.
• (Anything else that is missing but should be added here, edit or comment below.)
• A brief soft-reopening window, where any fix/stabilization CLs are okay to submit.
• Finally, open the tree for all general Go 1.25 changes.

CC @golang/release.

[gabyhelp]

Related Issues

• all: reopen tree for Go 1.24 development #67586 (closed)
• all: reopen tree for Go 1.22 development #61398 (closed)
• all: reopen tree for Go 1.23 development #64340 (closed)
• all: reopen tree for Go 1.23 development #65136 (closed)
• all: reopen tree for Go 1.22 development #60558 (closed)
• all: reopen tree for Go 1.21 development #57736 (closed)
• all: reopen tree for Go 1.19 development #51336 (closed)
• all: reopen tree for Go 1.20 development #53812 (closed)
• all: reopen tree for Go 1.18 development #47351 (closed)
• all: reopen tree for Go 1.17 development #44222 (closed)

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