From 14b2ffaf7ffdd199937e8bcba8b459da5491bcb6 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 28 Jun 2021 18:05:46 -0400 Subject: [PATCH] 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.) --- src/tools/RELEASE_CHANGES | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/src/tools/RELEASE_CHANGES b/src/tools/RELEASE_CHANGES index fd9dae7e55..e8de724fcd 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.