I wanted to share some brief thoughts about what to expect about Go development over the next few months.
Go development is not isolated from world events; work on Go always comes second to more basic concerns like personal and family health and safety. Nearly all of us are working at reduced capacity these days. I expect that capacity to drop further over the next few months.
Keeping a normal routine is a helpful coping mechanism, though, and we are trying to do the best we can to keep Go development moving along, both for ourselves and for all of you. As of right now, the plan is still to follow the Go release cycle, meaning the development cycle ends April 30, and the release target date remains August 1. Especially with our reduced capacity, we're going to continue to be strict about the freeze cutoff.
The last release was delayed mostly because we discovered some release blockers late in the freeze during internal testing of Kubernetes. We're working with the Kubernetes team here to do that testing earlier and more often. And we'll be more transparent about filing public release-blocker issues to explain what is going on; apologies for not doing that last round.
The last release was not delayed by our accepting RISCV-specific changes after the freeze, but it was still a mistake to do that: it sends the wrong messages and isn't fair to others who we've turned away from submitting changes. We won't be making non-critical exceptions like that anymore.
If our own working capacity is reduced but we keep the same timelines, then we must reduce the scope of what we expect to be in the release. Some new features or planned won't make it. That's OK - we'll get them next time. We all need to accept that, for our own work and work by others.
Most of all, let's all please be extra kind and charitable with each other. It's always good advice to remember that you don't know what external stresses are affecting the person on the other end of the email, review thread, or GitHub comment, but it's especially important now.
Thank you, as always, for all your work on Go. We wouldn't be where we are today without you.