build: process for automatic release tags (#10133)

Make the release tagging consistent. Push to release branch to create a stable release; push to release-rc to release a new candidate.
2025-05-26 13:33:53 +02:00
parent ddd98a818a
commit 58c85fc9db
4 changed files with 212 additions and 6 deletions
@@ -0,0 +1,18 @@
+# Release Notes
+
+Files in this directory constitute manual release notes for a given release.
+When relevant, they should be created prior to that release so that they can
+be included in the corresponding tag message, etc.
+
+To add release notes for a release 1.2.3, create a file named `v1.2.3.md`
+consisting of an initial H2-level header and further notes as desired. For
+example:
+
+```
+## Major changes in v1.2.3
+
+- Files are now synchronized twice as fast on Tuesdays
+```
+
+The release notes will also be included in candidate releases (e.g.
+v1.2.3-rc.1).