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: |
This is the start of the Go 1.19 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 #51336 Change-Id: Ic4b3f2c04b1fa5c588cb6d62e829f2ed1864e511 Reviewed-on: https://go-review.googlesource.com/c/go/+/388376 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Trust: Alex Rakoczy <alex@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Alex Rakoczy <alex@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
CL 388376 has been merged for Go 1.19. Moving this to the 1.20 milestone. |
This issue is currently labeled as early-in-cycle for Go 1.19. |
Change https://go.dev/cl/420816 mentions this issue: |
This is the start of the Go 1.20 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 #53812. Change-Id: Ic8919a61c9b2f3139717434b9c776d1597175448 Reviewed-on: https://go-review.googlesource.com/c/go/+/420816 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com>
CL 420816 took care of this for the start of the 1.20 cycle. Moving this to the next. |
This is the start of the Go 1.20 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 golang#40705. For golang#53812. Change-Id: Ic8919a61c9b2f3139717434b9c776d1597175448 Reviewed-on: https://go-review.googlesource.com/c/go/+/420816 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com>
Change https://go.dev/cl/462456 mentions this issue: |
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>
CL submitted for Go 1.21. Move to 1.22. |
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: