diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2025-05-18 23:31:44 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2025-05-18 23:31:44 -0400 |
| commit | f8db5c7a3f91aa07d53592f6e6e6378e26c7b55d (patch) | |
| tree | fcd2e8d418f42c6dafe6a717a544f008139b3451 /src/tools | |
| parent | 2c6469d4cd8175349abfe8da89dd642bca68fcfa (diff) | |
| download | postgresql-master.tar.gz postgresql-master.zip | |
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
Diffstat (limited to 'src/tools')
| -rw-r--r-- | src/tools/RELEASE_CHANGES | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/tools/RELEASE_CHANGES b/src/tools/RELEASE_CHANGES index 94c5a0f3bfb..c0d75c213be 100644 --- a/src/tools/RELEASE_CHANGES +++ b/src/tools/RELEASE_CHANGES @@ -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" |