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.25 development #70525

Closed
7 tasks done
dmitshur opened this issue Nov 22, 2024 · 7 comments
Closed
7 tasks done

all: reopen tree for Go 1.25 development #70525

dmitshur opened this issue Nov 22, 2024 · 7 comments
Assignees
@cagedmantis
Labels
early-in-cycle A change that should be done early in the 3 month dev cycle. NeedsFix The path to resolution is known, but the work has not been done. umbrella
Milestone
Go1.25

Comments

@dmitshur
Copy link
Contributor

dmitshur commented Nov 22, 2024 •
edited
Loading

Current Tree Status: Tree is open for Go 1.25 development (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.)
  • 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.
  • Submit CL for io/fs: add ReadLinkFS interface #49580.
  • (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.
@dmitshur dmitshur added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. early-in-cycle A change that should be done early in the 3 month dev cycle. umbrella labels Nov 22, 2024
@dmitshur dmitshur added this to the Go1.25 milestone Nov 22, 2024
@gabyhelp
Copy link

Related Issues

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

@dmitshur dmitshur moved this to Planned in Go Release Nov 22, 2024
@dmitshur dmitshur mentioned this issue Dec 4, 2024
Closed
@cagedmantis cagedmantis self-assigned this Jan 29, 2025
@gopherbot
Copy link
Contributor

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

gopherbot pushed a commit that referenced this issue Feb 3, 2025
@cherrymui
internal/goversion: update Version to 1.25
9da530f 
Go 1.25 is in the process of being opened for development (to be
eventually released). This change marks the very beginning of its
development cycle, updating the Version value accordingly.

For #40705.
For #70525.

Change-Id: If673d4aeddc376fefe6bddc3ec2704ca91245777
Reviewed-on: https://go-review.googlesource.com/c/go/+/646155
Reviewed-by: Carlos Amedee <carlos@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
@gopherbot
Copy link
Contributor

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

gopherbot pushed a commit that referenced this issue Feb 3, 2025
@cherrymui
doc: initialize next directory for Go 1.25
e2f342f 
Following the "For the release team" steps in README:

	cd doc
	cp -R initial/ next
	$EDITOR next/1-intro.md

For #70525

Change-Id: I31c271d95ccd72123f531fde4e72929ec7b310d9
Reviewed-on: https://go-review.googlesource.com/c/go/+/646195
Reviewed-by: Carlos Amedee <carlos@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Feb 3, 2025
@dmitshur dmitshur moved this from Planned to In Progress in Go Release Feb 3, 2025
@gopherbot
Copy link
Contributor

This issue is currently labeled as early-in-cycle for Go 1.25.
That time is now, so a friendly reminder to look at it again.

@cherrymui
Copy link
Member

Done.

@github-project-automation github-project-automation bot moved this from In Progress to Done in Go Release Feb 4, 2025
@mateusz834
Copy link
Member

FYI, go.mod still say go 1.24

go/src/go.mod

Line 3 in ee6e0a5

go 1.24

Not sure whether this needs to be changed too, looking at blame it was changed with deps update before (CL 600535). I noticed this because i had not updated my $PATH, thus:

[mateusz@arch src (master)]$ go version
go: downloading go1.24.0 (linux/amd64)

@cherrymui
Copy link
Member

Thanks for bringing this up. Updating the vendored dependencies is #36905, which I plan to do later this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cagedmantis cagedmantis

Labels
early-in-cycle A change that should be done early in the 3 month dev cycle. NeedsFix The path to resolution is known, but the work has not been done. umbrella
Projects
Go Release
Archived in project
Milestone
Go1.25
Development

No branches or pull requests
6 participants
@cagedmantis @dmitshur @gopherbot @cherrymui @mateusz834 @gabyhelp