Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upinternal/goversion: increment Version at start of cycle #40705
Milestone
Comments
|
Change https://golang.org/cl/248038 mentions this issue: |
dmitshur
changed the title
gopherbot
pushed a commit
that referenced
this issue
Aug 12, 2020
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
goversion.Versionneeds 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 @cagedmantis @toothrot @andybons @heschik @bcmills