Skip to content

/ go

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

Jump to bottom

internal/goversion: increment Version at start of cycle #40705

Open
dmitshur opened this issue Aug 11, 2020 · 4 comments
Open

internal/goversion: increment Version at start of cycle #40705

dmitshur opened this issue Aug 11, 2020 · 4 comments
Labels
NeedsFix early-in-cycle recurring release-blocker
Milestone
Go1.18

Comments

@dmitshur
Copy link
Member

@dmitshur dmitshur commented Aug 11, 2020

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 @cagedmantis @toothrot @andybons @heschik @bcmills
@dmitshur dmitshur self-assigned this Aug 11, 2020
@dmitshur dmitshur mentioned this issue Aug 11, 2020
Closed
@gopherbot
Copy link

@gopherbot gopherbot commented Aug 11, 2020

Change https://golang.org/cl/248038 mentions this issue: internal/goversion: update Version to 1.16
@dmitshur dmitshur changed the title internal/goversion: increment Version internal/goversion: increment Version at start of cycle Aug 11, 2020
@dmitshur dmitshur removed their assignment Aug 11, 2020
gopherbot pushed a commit that referenced this issue Aug 12, 2020
@dmitshur
internal/goversion: update Version to 1.16
813b6bb 
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>
@dmitshur dmitshur added this to the Go1.16 milestone Aug 12, 2020
@dmitshur
Copy link
Member Author

@dmitshur dmitshur commented Aug 12, 2020

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.
@dmitshur dmitshur modified the milestones: Go1.16, Go1.17 Aug 12, 2020
@gopherbot
Copy link

@gopherbot gopherbot commented Dec 3, 2020

Change https://golang.org/cl/275297 mentions this issue: internal/goversion: update Version to 1.17
@bcmills
Copy link
Member

@bcmills bcmills commented Feb 16, 2021

CL 275297 merged for Go 1.17. Moving to 1.18.
gopherbot pushed a commit that referenced this issue Feb 16, 2021
@bcmills
internal/goversion: update Version to 1.17
5faf941 
(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>
@bcmills bcmills modified the milestones: Go1.17, Go1.18 Feb 16, 2021
@dmitshur dmitshur mentioned this issue Feb 18, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsFix early-in-cycle recurring release-blocker
Projects
None yet
Milestone
Go1.18
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@dmitshur @bcmills @gopherbot