mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Doc: further updates for RELEASE_CHANGES process notes.

Browse Source 
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.)
This commit is contained in:
Tom Lane 2021-06-28 18:05:46 -04:00
parent bc49ab3c27
commit 14b2ffaf7f
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
src/tools/RELEASE_CHANGES
View File

@ -107,8 +107,14 @@ Starting a New Development Cycle
placeholder), "git rm" the previous one, and update release.sgml and placeholder), "git rm" the previous one, and update release.sgml and
filelist.sgml to match. 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 * 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 Creating Back-Branch Release Notes
@ -141,8 +147,12 @@ Creating Back-Branch Release Notes
Retiring a Branch 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 * 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.