The early CLs have all landed (see issue 44222
), and the tree is now open for general development
for the Go 1.17 release.
The doc/go1.17.html draft file will be made available soon (it's CL 295209
), so you can start documenting your changes while they're fresh in memory (less work to do at the end of the release!). We will remove all "wait-release" tags on Gerrit CLs (to be replaced with "ex-wait-release"), as well as ping issues in the Go 1.17 milestone that are marked as "early-in-cycle".
I'll copy these points from our past tree reopenings, since they're helpful to keep in mind:
- Check build.golang.org Before Submitting
Before starting to submit your CL or a stack of CLs, please check that the tip is green at https://build.golang.org. If there is a widespread test failure, please wait, or better, help with efforts to diagnose and fix the failure.
- Revert Sooner
When a change that landed on master results in a confirmed failure or unintended behavior change, we ask everyone to revert that change sooner, instead of letting it stay merged. For example, if we learn that a change in unspecified behavior of a function like url.Parse causes breakage, then it is better to roll back while thinking about how to address the issue.
This helps ensure master is more stable, making it easier for people who are developing other changes.
- Freeze Exceptions
Any exceptions to the freeze must be communicated to and explicitly approved by the Go Release Team before the freeze. If you’d like to request an exception, please start a thread on golang-dev or file an issue in the issue tracker with “[freeze exception]” as a suffix (example). We will address any requests on a case-by-case basis with a strong preference for not permitting changes after the freeze.
Changes that are not in line will be reverted on master and asked to be re-sent during the next cycle.
As always, please proceed cautiously, and happy Go 1.17 development!