Skip to content

all: reopen tree for Go 1.23 development #64340

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

Closed
4 tasks done
mknyszek opened this issue Nov 22, 2023 · 4 comments
Closed
4 tasks done

all: reopen tree for Go 1.23 development #64340

mknyszek opened this issue Nov 22, 2023 · 4 comments
Assignees
Labels
early-in-cycle A change that should be done early in the 3 month dev cycle. FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. umbrella
Milestone

Comments

@mknyszek
Copy link
Contributor

mknyszek commented Nov 22, 2023

Current Tree Status: Tree is open for Go 1.23 development

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

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

  • Bump internal/goversion.Version to 23 and update the go directive in the go.mod files —this should be the very first CL to be submitted as it marks the start of master branch representing Go 1.23 (rather than Go 1.22). (Example CL.)
  • Any CLs associated with issues labelled as early-in-cycle.
  • Submit CLs that are already approved and marked AutoSubmit, but blocked on wait-release
  • Finally, open the tree for all general Go 1.23 changes.

CC @golang/release.

@mknyszek mknyszek added NeedsFix The path to resolution is known, but the work has not been done. early-in-cycle A change that should be done early in the 3 month dev cycle. umbrella labels Nov 22, 2023
@mknyszek mknyszek added this to the Go1.23 milestone Nov 22, 2023
@Goclipse27

This comment was marked as spam.

@Goclipse27

This comment was marked as spam.

@gopherbot
Copy link
Contributor

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

gopherbot pushed a commit that referenced this issue Jan 19, 2024
(The corresponding update for the last release cycle was CL 510735.)

For #40705
For #64340

Change-Id: I123ce68131a6c7b0344cab54cd29402cabb57225
Reviewed-on: https://go-review.googlesource.com/c/go/+/557155
Reviewed-by: Dmitri Shuralyov <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
LUCI-TryBot-Result: Go LUCI <[email protected]>
@dmitshur dmitshur moved this to In Progress in Go Release Jan 19, 2024
@dmitshur dmitshur assigned cherrymui and unassigned cagedmantis Jan 22, 2024
@cherrymui
Copy link
Member

Tree reopened.

@github-project-automation github-project-automation bot moved this from In Progress to Done in Go Release Jan 22, 2024
ezz-no pushed a commit to ezz-no/go-ezzno that referenced this issue Feb 18, 2024
(The corresponding update for the last release cycle was CL 510735.)

For golang#40705
For golang#64340

Change-Id: I123ce68131a6c7b0344cab54cd29402cabb57225
Reviewed-on: https://go-review.googlesource.com/c/go/+/557155
Reviewed-by: Dmitri Shuralyov <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
LUCI-TryBot-Result: Go LUCI <[email protected]>
@golang golang locked and limited conversation to collaborators Jan 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
early-in-cycle A change that should be done early in the 3 month dev cycle. FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. umbrella
Projects
Archived in project
Development

No branches or pull requests

5 participants