Currently, language change proposals created through the corresponding template are given titles starting with "proposal: Go 2:" and assigned LanguageChange and v2 labels. As an outsider to the process, there are a number of reasons this is confusing.

• "Go 2" in other contexts usually refers to changes that cannot be made in a backward compatible manner, requiring a (major) version 2 of Go. However, the Go team has already announced the decision that a version 2 of Go will never exist. And notably, now that math/rand/v2: revised API for math/rand #61716 has opened up the opportunity for v2 standard library packages, it seems like the only truly backward incompatible changes are language changes.
• The LanguageChange and v2 labels have enormous overlap. There are currently eight open issues which are LanguageChange and not v2 (all of which are titled "proposal: spec:" instead of "proposal: Go 2:") and forty-one open issues which are v2 and not LanguageChange (all of which are over three years old), versus eighty-eight which are both. I learned while writing this issue that the v2 label has a description that it includes "incompatible library changes," and indeed most of the non-language-change v2 issues are of that sort, but math/rand/v2: revised API for math/rand #61716 never carried it.
• As mentioned, a different way to create a language change proposal is to say "proposal: spec:". Many of the issues titled this way are also labeled LanguageChange and v2; some are not, which in practice has made it hard for me to find particular proposals when answering questions. (There are also many issues titled like "proposal: Go 2: spec:".)
• proposal: review meeting minutes #33502 and proposal: Go 2 review meeting minutes #33892 both sometimes mention issues titled as either "Go 2" or "spec." Some "spec" language changes, e.g. spec: add range over int, range over func #61405 and spec: add clear(x) builtin, to clear map, zero content of slice #56351, never appeared in the latter.

While I recognize that the situation reflects processes of the respective proposal review teams, it is not intuitive and sometimes actively interferes with outside usage. In particular, the question of why backward compatible language change proposals are titled "Go 2" comes up often. (Most recently this occurred in #65652 (comment), but I recall several other instances on the issue tracker, and I've explained it frequently in other channels as well.) It's also worth noting that the document explaining the proposal process doesn't explain what "Go 2" means.

There are a few measures which I suggest to reduce the confusion around language change proposal triage and make searching more consistent:

• Title all language change proposals as "proposal: spec:" and drop the "Go 2" moniker. Then the most common question disappears entirely.
• Label all "proposal: spec:" issues as LanguageChange. Then it's easy to narrow a search to all language change proposals. (Strictly speaking, this isn't necessary if the previous item is implemented, since one could search for "proposal: spec:" in:title, but that phrasing makes it hard to search issue and comment text as well.)
• Apply the v2 label to backward-incompatible changes only. Ostensibly, these should either be for standard library packages – which will actually be v2 – or rejected as infeasible almost immediately. This would likely require manual intervention during triage.