all: reopen tree for Go 1.17 development

[dmitshur]

Current Tree Status: Open for Go 1.17 development (see golang-dev announcement)

As we're getting closer to the final Go 1.16 release, we will soon need to open the tree for Go 1.17 development.

As usual, the tree will initially be open to changes that must land early. Tentatively:

• CL 275297 that bumps internal/goversion—this must be the very first CL to be submitted; CC @bcmills
• dev.regabi branch will be merged to master as described here—tracking issue all: merge dev.regabi to master when tree reopens #44224; CC @cherrymui, @jeremyfaller
• dev.typeparam branch will be merged to master assuming the proposal is accepted; CC @griesemer, @jeremyfaller
• windows/arm64 @rsc
• cmd/go lazy loading refactoring @bcmills
• //go:build changes @rsc
• (Add/reorder any other CLs or stacks or branches that must land early.)
• Finally, open the tree for all general Go 1.17 changes.

We will send status updates to golang-dev@ as part of this work.

This is the tracking issue for completing this task.

CC @golang/release, @ianlancetaylor.

[dmitshur]

It's planned by @golang/release for this issue to begin progressing after the Go 1.16 release is issued.

[dmitshur]

The "Current Tree Status" was just changed from "Frozen for Go 1.16 changes only" to "Accepting early Go 1.17 changes only (see list below)". I've sent a message to golang-dev.

I'll work with @bcmills on the first CL on the list.

[bcmills]

internal/goversion is in. Time to merge some branches (@cherrymui, @jeremyfaller)?

[gopherbot]

Change https://golang.org/cl/292709 mentions this issue: all: merge branch dev.regabi (d3cd4830ad) into master

[dmitshur]

Merging dev.regabi into master (issue #44224) was resolved (thank you @cherrymui). The next item currently in the list is:

• dev.typeparam branch will be merged to master assuming the proposal is accepted; CC @griesemer, @jeremyfaller

When it's done (or if plans change), please update this issue and coordinate with the people working on the next item. Thank you!

[griesemer]

Quick update. Merging the dev.typeparams branch will require 1) to merge master into dev.typeparams (today), 2) isolating API changes that we may need for 1.18 but not for 1.17 (next couple of days), and then 3) merging dev.typeparams into master (hopefully by end of this week).