Add process doc for C++ major version upgrades.
Bug: none
Change-Id: I126e5905ddde8b1daf761be3bb6300bcd7062118
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6325555
Reviewed-by: Rick Byers <[email protected]>
Auto-Submit: Peter Kasting <[email protected]>
Commit-Queue: Peter Kasting <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1434432}
diff --git a/styleguide/c++/c++-features.md b/styleguide/c++/c++-features.md
index a83b97f2..ecce26b 100644
--- a/styleguide/c++/c++-features.md
+++ b/styleguide/c++/c++-features.md
@@ -9,11 +9,13 @@
support._
The C++ language has in recent years received an updated standard every three
-years (C++11, C++14, etc.). For various reasons, Chromium does not immediately
-allow new features on the publication of such a standard. Instead, once
-Chromium supports the toolchain to a certain extent (e.g., build support is
-ready), a standard is declared "_initially supported_", with new
-language/library features banned pending discussion but not yet allowed.
+years (C++11, C++14, etc.).
+[For various reasons](https://chromium.googlesource.com/chromium/src/+/main/docs/process/c++_version_upgrades.md),
+Chromium does not immediately allow new features on the publication of such a
+standard. Instead, once Chromium supports the toolchain to a certain extent
+(e.g., build support is ready), a standard is declared "_initially supported_",
+with new language/library features banned pending discussion but not yet
+allowed.
You can propose changing the status of a feature by sending an email to
[[email protected]](https://groups.google.com/a/chromium.org/forum/#!forum/cxx).
