From: Jonathan Amsterdam Date: Fri, 26 Apr 2024 18:47:37 +0000 (-0400) Subject: doc/README.md: discourage RELNOTE in CLs X-Git-Tag: go1.23rc1~513 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=0e7f5cf30ba43f4d388803642b4173e5af20e761;p=gostls13.git doc/README.md: discourage RELNOTE in CLs Release notes should always be files under doc/next. Make it clear that this is the only way to add them: RELNOTE markers in CLs are no longer supported. Change-Id: I34d77eb876f57b84ecdc7e5ecbf3eb5c91e6fed8 Reviewed-on: https://go-review.googlesource.com/c/go/+/582075 Reviewed-by: Dmitri Shuralyov TryBot-Bypass: Jonathan Amsterdam Reviewed-by: Dmitri Shuralyov --- diff --git a/doc/README.md b/doc/README.md index 666e0966c9..c2b320711f 100644 --- a/doc/README.md +++ b/doc/README.md @@ -4,7 +4,9 @@ The `initial` and `next` subdirectories of this directory are for release notes. ## For developers -Release notes should be added to `next` by editing existing files or creating new files. +Release notes should be added to `next` by editing existing files or creating +new files. **Do not add RELNOTE=yes comments in CLs.** Instead, add a file to +the CL (or ask the author to do so). At the end of the development cycle, the files will be merged by being concatenated in sorted order by pathname. Files in the directory matching the