Merge branch 'golang:master' into master

api/README

@@ -21,3 +21,6 @@ warning output from the go api tool. Each file should be named
 nnnnn.txt, after the issue number for the accepted proposal.
 (The #nnnnn suffix must also appear at the end of each line in the file;
 that will be preserved when next/*.txt is concatenated into go1.XX.txt.)
+
+When you add a file to the api/next directory, you must add at least one file
+under doc/next. See doc/README.md for details.

api/go1.22.txt

@@ -1,13 +1,4 @@
 pkg archive/tar, method (*Writer) AddFS(fs.FS) error #58000
-pkg archive/tar, type FileInfoNames interface { Gname, IsDir, ModTime, Mode, Name, Size, Sys, Uname } #50102
-pkg archive/tar, type FileInfoNames interface, Gname(int) (string, error) #50102
-pkg archive/tar, type FileInfoNames interface, IsDir() bool #50102
-pkg archive/tar, type FileInfoNames interface, ModTime() time.Time #50102
-pkg archive/tar, type FileInfoNames interface, Mode() fs.FileMode #50102
-pkg archive/tar, type FileInfoNames interface, Name() string #50102
-pkg archive/tar, type FileInfoNames interface, Size() int64 #50102
-pkg archive/tar, type FileInfoNames interface, Sys() interface{} #50102
-pkg archive/tar, type FileInfoNames interface, Uname(int) (string, error) #50102
 pkg archive/zip, method (*Writer) AddFS(fs.FS) error #54898
 pkg cmp, func Or[$0 comparable](...$0) $0 #60204
 pkg crypto/x509, func OIDFromInts([]uint64) (OID, error) #60665

api/next/42888.txt

@@ -0,0 +1 @@
+pkg runtime/debug, func SetCrashOutput(*os.File) error #42888

api/next/61696.txt

@@ -0,0 +1 @@
+pkg sync, method (*Map) Clear() #61696

doc/README.md

@@ -0,0 +1,46 @@
+# Release Notes
+
+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.
+
+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
+glob "*stdlib/*minor" are treated specially. They should be in subdirectories
+corresponding to standard library package paths, and headings for those package
+paths will be generated automatically.
+
+Files in this repo's `api/next` directory must have corresponding files in
+`doc/next/*stdlib/*minor`.
+The files should be in the subdirectory for the package with the new
+API, and should be named after the issue number of the API proposal.
+For example, if the directory `6-stdlib/99-minor` is present,
+then an `api/next` file with the line
+
+    pkg net/http, function F #12345
+
+should have a corresponding file named `doc/next/6-stdlib/99-minor/net/http/12345.md`.
+At a minimum, that file should contain either a full sentence or a TODO,
+ideally referring to a person with the responsibility to complete the note.
+
+Use the following forms in your markdown:
+
+	[`http.Request`](/pkg/net/http#Request)         # symbol documentation
+	[#12345](/issue/12345)                          # GitHub issues
+	[CL 6789](/cl/6789)                             # Gerrit changelists
+
+## For the release team
+
+At the start of a release development cycle, the contents of `next` should be deleted
+and replaced with those of `initial`. From the repo root:
+
+    > cd doc
+    > rm -r next/*
+    > cp -r initial/* next
+
+Then edit `next/1-intro.md` to refer to the next version.
+
+To prepare the release notes for a release, run `golang.org/x/build/cmd/relnote generate`.
+That will merge the `.md` files in `next` into a single file.