Current Tree Status: Release freeze for Go 1.27 (see golang-dev announcement)
Now that we've entered the freeze for Go 1.27, we will eventually need to reopen the tree for Go 1.28 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 July 2026 (see https://go.dev/s/release#timeline), exact timing depends on how well the Go 1.27 release preparations are going.
This is the currently planned tree reopening sequence:
CC @golang/release, @cherrymui, @aclements.
Current Tree Status: Release freeze for Go 1.27 (see golang-dev announcement)
Now that we've entered the freeze for Go 1.27, we will eventually need to reopen the tree for Go 1.28 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 July 2026 (see https://go.dev/s/release#timeline), exact timing depends on how well the Go 1.27 release preparations are going.
This is the currently planned tree reopening sequence:
internal/goversion.Versionto 28—this should be the very first CL to be submitted as it marks the start of main branch representing Go 1.28 (rather than Go 1.27). (Example CL.)doc/nextfor the Go 1.28 cycle. (See "For the release team" in doc/README.)CC @golang/release, @cherrymui, @aclements.