Understanding the Go 2 Proposal Process and How to Track Future Language Changes

Go language has remained at its first major version since 2008, and the term "Go 2" is used as a nickname for future language updates and new features rather than a formal second major release.

While Go 1 is maintained by a small core team, Go 2 will be largely community‑driven; developers are submitting an increasing number of proposals, and a standardized process is being applied to select and evaluate them.

Proposal selection criteria: 1. Solves an important problem for many users. 2. Has negligible negative impact. 3. Provides a clear and understandable solution.

Proposal evaluation workflow: 1. Proposal selection : Go team filters a few proposals worth considering. 2. Proposal feedback : Announce selected proposals, explain intent, and collect feedback. 3. Implementation : Implement proposals based on feedback in preparation for a release. 4. Implementation feedback : Developers try new features during the development cycle and provide further feedback. 5. Launch decision : Assess whether expected benefits were achieved or any unexpected costs arose, then decide to adopt, reject, or continue discussion.

To view the actual proposals and their status, browse GitHub issues labeled Go2 and Proposal . Labels such as LanguageChange , NeedsDecision , NeedsInvestigation , and Proposal‑Accepted indicate the nature and current state of each proposal.

For early experimentation, visit the Go releases page (https://github.com/golang/go/releases) and explore the listed releases; the "Reviewed‑on" links provide detailed change information.

The most reliable source for comprehensive updates is the official Go blog and documentation at https://blog.golang.org/index, where all information is systematically summarized.