database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-29 16:21:20 +03:00
Code

Doc: add pre-branch task to run src/tools/copyright.pl.

Browse Source 
It's common for some files with last year's copyright date
to sneak into the tree between early January (when we normally run
copyright.pl) and feature freeze.  Immediately before branching
the new release is an ideal time to fix the stragglers, so add a
note about it to the RELEASE_CHANGES checklist.

Discussion: https://postgr.es/m/CALa6HA4_Wu7-2PV0xv-Q84cT8eG7rTx6bdjUV0Pc=McAwkNMfQ@mail.gmail.com
This commit is contained in:
Tom Lane 2025-05-18 23:31:44 -04:00
parent 2c6469d4cd
commit f8db5c7a3f
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/tools/RELEASE_CHANGES
View File

@ -89,6 +89,9 @@ Starting a New Development Cycle
* Typically, we do pgindent and perltidy runs just before branching,
as well as before beta (complete steps from src/tools/pgindent/README)
* It's also advisable to check that copyright years are up-to-date
(run src/tools/copyright.pl, commit any changes it finds)
* Create a branch in git for maintenance of the previous release
o on master branch, do:
git pull # be sure you have the latest "master"