aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-06-28 18:05:46 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-06-28 18:05:46 -0400
commit14b2ffaf7ffdd199937e8bcba8b459da5491bcb6 (patch)
treed24e0c713391535c190fda1c7bf9b197e77274f6
parentbc49ab3c277b6b478bdad80c1ae36f926a33b4a6 (diff)
downloadpostgresql-14b2ffaf7ffdd199937e8bcba8b459da5491bcb6.tar.gz
postgresql-14b2ffaf7ffdd199937e8bcba8b459da5491bcb6.zip
Doc: further updates for RELEASE_CHANGES process notes.
Mention expectations for email notifications of appropriate lists when a branch is made or retired. (I've been doing that informally for years, but it's better to have it written down.)
-rw-r--r--src/tools/RELEASE_CHANGES14
1 files changed, 12 insertions, 2 deletions
diff --git a/src/tools/RELEASE_CHANGES b/src/tools/RELEASE_CHANGES
index fd9dae7e55d..e8de724fcd8 100644
--- a/src/tools/RELEASE_CHANGES
+++ b/src/tools/RELEASE_CHANGES
@@ -107,8 +107,14 @@ Starting a New Development Cycle
placeholder), "git rm" the previous one, and update release.sgml and
filelist.sgml to match.
+* Notify the private committers email list, to ensure all committers
+ are aware of the new branch even if they're not paying close attention
+ to pgsql-hackers.
+
* Get the buildfarm's 'branches_of_interest.txt' file updated with the new
- branch.
+ branch. Once the buildfarm server is accepting reports, notify the
+ buildfarm owners' email list, for the benefit of owners who use manual
+ branch scheduling.
Creating Back-Branch Release Notes
@@ -141,8 +147,12 @@ Creating Back-Branch Release Notes
Retiring a Branch
=================
+* Notify the private committers email list, to ensure all committers
+ are aware of the branch being dead.
+
* Get the buildfarm's 'branches_of_interest.txt' file updated to remove
- the retired branch.
+ the retired branch. Then notify the buildfarm owners' email list,
+ for the benefit of owners who use manual branch scheduling.