-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
internal/goversion: increment Version at start of cycle #40705
Comments
Change https://golang.org/cl/248038 mentions this issue: |
This is the start of the Go 1.16 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). Historically, we used to bump this at an arbitrary time throughout the development cycle, but it's better to be more predictable about updating it. The start of a development cycle should be the most appropriate time: it clearly marks the boundary between 1.15 and 1.16 development, and doing it early can help catch issues in other tooling. See issue #38704 for more background. There is no longer a need to update the list of Go versions in src/go/build/doc.go because it does not exist as of CL 232981. For #40705. Updates #38704. Updates #37018. Change-Id: Id8ee733b5e79c53b6cd03509c6560614d8743833 Reviewed-on: https://go-review.googlesource.com/c/go/+/248038 Reviewed-by: Carlos Amedee <carlos@golang.org>
CL 248038 took care of this for the Go 1.16 cycle, so moving this issue to be looked at at the start of the Go 1.17 cycle. |
Change https://golang.org/cl/275297 mentions this issue: |
CL 275297 merged for Go 1.17. Moving to 1.18. |
(The corresponding update for the last release cycle was CL 248038.) For #40705. Change-Id: I13becdc4c3718a1c6986876ec56879cce3bcb34f Reviewed-on: https://go-review.googlesource.com/c/go/+/275297 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Change https://golang.org/cl/341590 mentions this issue: |
This is the start of the Go 1.18 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). Updates #40705 Updates #47351 Change-Id: Icfb99e28529a3c9fb7394e114a34586f613dfcbf Reviewed-on: https://go-review.googlesource.com/c/go/+/341590 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Alexander Rakoczy <alex@golang.org>
CL 341590 has been merged for Go 1.18. Moving this to the 1.19 milestone. |
Change https://go.dev/cl/388376 mentions this issue: |
For #40705. Change-Id: I06df5f4ea5cf65420c2dac754a1e65ac819c1090 Reviewed-on: https://go-review.googlesource.com/c/go/+/510735 Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Eli Bendersky <eliben@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com>
This issue is currently labeled as early-in-cycle for Go 1.22. |
CL 510735 took care of this for 1.22. Moving to 1.23. |
Change https://go.dev/cl/557155 mentions this issue: |
(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 <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
This issue is currently labeled as early-in-cycle for Go 1.23. |
CL 557155 took care of this for 1.23. Moving to 1.24. |
(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 <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Change https://go.dev/cl/600176 mentions this issue: |
Go 1.24 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 #67586. Change-Id: Ibd194f229e7dbd25bc2713f86330fab50ea1dfaa Reviewed-on: https://go-review.googlesource.com/c/go/+/600176 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
CL 600176 did this for Go 1.24; moving to the next milestone. |
Change https://go.dev/cl/646155 mentions this issue: |
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>
This issue is currently labeled as early-in-cycle for Go 1.25. |
CL 646155 did this for Go 1.25. Bump to the next cycle. |
goversion.Version
needs to be incremented by one at the start of each development cycle, to match the upcoming major Go release version.Once done, this issue should be moved to the next major release milestone.
(CC @golang/release.)
The text was updated successfully, but these errors were encountered: