Skip to content
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.

Sign up for GitHub

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

Jump to bottom

all: reopen tree for Go 1.21 development #57736

Closed
5 tasks done
cagedmantis opened this issue Jan 11, 2023 · 3 comments
Closed
5 tasks done

all: reopen tree for Go 1.21 development #57736

cagedmantis opened this issue Jan 11, 2023 · 3 comments
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
Go1.21

Comments

@cagedmantis
Copy link
Contributor

cagedmantis commented Jan 11, 2023 •
edited by cherrymui

Current Tree Status: Tree open for Go 1.21 general development

This is a tracking issue for the upcoming task of reopening the tree for Go 1.21 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 21—this should be the very first CL to be submitted as it marks the start of master branch representing Go 1.21 (rather than Go 1.20). (Example CL.)
  • Large stack of go/types changes go.dev/cl/461495 (@griesemer)
  • Stack of reproducibility-related and go.env fixes CL 462199 and parents (@rsc)
  • [ ] Any CLs associated with issues labelled as early-in-cycle. (Detailed list being compiled) (None)
  • Submit CLs that are already approved and marked AutoSubmit, but blocked on wait-release
  • Finally, open the tree for all general Go 1.21 changes.

CC @golang/release.
@cagedmantis cagedmantis 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 Jan 11, 2023
@cagedmantis cagedmantis added this to the Go1.21 milestone Jan 11, 2023
@bcmills
Copy link
Contributor

bcmills commented Jan 11, 2023

Note that since we now have Auto-Submit and it knows about the No-Wait-Release condition, we should be careful not to remove wait-release CL hashtags until the tree is fully open for general changes.

@gopherbot
Copy link

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

gopherbot pushed a commit that referenced this issue Jan 17, 2023
@cherrymui
internal/goversion: update Version to 1.21
83f8688 
This is the start of the Go 1.21 development cycle, so update the
Version value accordingly. It represents the Go 1.x version that
will soon open up for development (and eventually become released).

For #40705.
For #57736.

Change-Id: I31b739f632bdc8d14f46560e0e5bf333fb8e7740
Reviewed-on: https://go-review.googlesource.com/c/go/+/462456
Reviewed-by: Carlos Amedee <carlos@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
Run-TryBot: Cherry Mui <cherryyz@google.com>
@cherrymui
Copy link
Member

The tree is open now. Thanks.

@golang golang locked and limited conversation to collaborators Jan 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
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
Go Release
Archived in project
Milestone
Go1.21
Development

No branches or pull requests
4 participants
@cagedmantis @bcmills @gopherbot @cherrymui