README.md: mention GODEBUG settings
Change-Id: Icf2c7f06a2a3a391f535738b5014375bd37bbc0e
Reviewed-on: https://go-review.googlesource.com/c/proposal/+/572015
Commit-Queue: Russ Cox <rsc@golang.org>
Reviewed-by: Russ Cox <rsc@golang.org>
diff --git a/README.md b/README.md
index ef81d7d..7b161c2 100644
--- a/README.md
+++ b/README.md
@@ -68,9 +68,16 @@
The proposal process should be used for any notable change or addition to the
language, libraries and tools.
-“Notable” includes API changes in the main repo and all golang.org/x repos,
-as well as command-line changes to the `go` command.
-It also includes visible behavior changes in existing functionality.
+“Notable” includes (but is not limited to):
+
+- API changes in the main repo and all golang.org/x repos.
+- Command-line changes to the `go` command.
+- Any visible behavior changes that need a [GODEBUG setting](https://go.dev/doc/godebug) for compatibility.
+- Any other visible behavior changes in existing functionality.
+- Adoption or use of new protocols, protocol versions, cryptographic algorithms, and the like,
+ even in an implementation.
+ Such changes are externally visible and require discussion and probably a GODEBUG setting.
+
Since proposals begin (and will often end) with the filing of an issue, even
small changes can go through the proposal process if appropriate.
Deciding what is appropriate is matter of judgment we will refine through
