[SCM] PostGIS branch master updated. 3.7.0beta2-46-g40b61a5fc

Sat Aug 15 09:57:21 PDT 2026

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "PostGIS".

The branch, master has been updated
       via  40b61a5fc02f0bb2d07be263e180e7f24c6c5a95 (commit)
       via  1e4de3b9810b2c1f54be73d74011e1b9389bd958 (commit)
      from  a87600d95611a7c22487f0fa01155bd2fe17f6a2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 40b61a5fc02f0bb2d07be263e180e7f24c6c5a95
Merge: a87600d95 1e4de3b98
Author: Darafei Praliaskouski <komzpa at gmail.com>
Date:   Sat Aug 15 09:57:20 2026 -0700

    Merge pull request 'docs: document NEWS entry workflow' (!734) from Komzpa/postgis:docs/news-guide-20260813 into master
    
    Add a concise maintainer checklist for PostGIS NEWS entries. It covers entry scope, placement, attribution, release preparation, checker commands, and backpatch wording.
    
    The guide uses neutral examples and keeps the base-ref and released-entry rules explicit.
    
    Reviewed-on: https://gitea.osgeo.org/postgis/postgis/pulls/734


commit 1e4de3b9810b2c1f54be73d74011e1b9389bd958
Author: Darafei Praliaskouski <me at komzpa.net>
Date:   Thu Aug 13 20:59:21 2026 +0400

    docs: document NEWS entry workflow

diff --git a/doc/development/maintenance/_index.md b/doc/development/maintenance/_index.md
index 312010bb3..27dc9f2c5 100644
--- a/doc/development/maintenance/_index.md
+++ b/doc/development/maintenance/_index.md
@@ -66,8 +66,10 @@ OSGeo legal counsel before committing.
 
 For the maintained commit-message, branch-target, authorship, and post-push
 rules distilled from RFC-5, see [Commit and branch guidelines](commit-guidelines.md).
-For supported-branch fix propagation, provenance, `NEWS`, and Trac follow-up
-rules, see [Backpatching fixes](backpatching.md).
+For `NEWS` wording, prerelease sections, release cleanup, and checker rules,
+see [NEWS entries](news.md). For supported-branch fix propagation, provenance,
+branch-local `NEWS`, and Trac follow-up rules, see
+[Backpatching fixes](backpatching.md).
 For labels, milestones, draft state, and mirror metadata on pull requests, see
 [Pull request metadata](pull-request-metadata.md).
 
@@ -191,8 +193,9 @@ Before backpatching, confirm the target release line is open in `Version.config`
 and `NEWS`. Stable branches normally receive bug fixes, not new features. End of
 life branches should not receive new work without explicit release-manager
 direction.
-Use [Backpatching fixes](backpatching.md) for the two-pass branch
-scan, one-to-one commit provenance, `NEWS` expectations, and per-ticket Trac
+Use [NEWS entries](news.md) for wording, credit, release cleanup, and checker
+rules. Use [Backpatching fixes](backpatching.md) for the two-pass branch scan,
+one-to-one commit provenance, branch-local `NEWS`, and per-ticket Trac
 follow-up wording.
 
 During pre-release code freeze, restrict commits to bug fixes unless the PSC or
diff --git a/doc/development/maintenance/news.md b/doc/development/maintenance/news.md
new file mode 100644
index 000000000..5adb7c86a
--- /dev/null
+++ b/doc/development/maintenance/news.md
@@ -0,0 +1,90 @@
+---
+title: "NEWS Entries"
+date: 2026-08-13
+weight: 25
+geekdocHidden: false
+---
+
+`NEWS` is a short release changelog, not a commit log.
+
+## Add
+
+Add an entry for a user-visible or release-worthy:
+
+* breaking change, feature, or enhancement;
+* bug, security, or memory-safety fix;
+* stable-branch fix or ticketed behavior change.
+
+Skip refactors, tests, CI, and packaging unless release users or packagers need
+to know.
+
+Describe the behavior, not the branch, review, or test run:
+
+```text
+ - #NNNN, [subsystem] Brief behavior summary
+          (Contributor Name)
+```
+
+Use `#NNNN` for Trac, `GH-NNN` for GitHub, and `GT-NNN` for Gitea. Do not use
+bare `#NNNN` for GitHub or Gitea. Keep subsystem tags consistent with nearby
+entries.
+
+Credit authors in the final parentheses. For a reported security fix, use
+`reported by ...; fixed by ...` when the roles differ. If the reporter supplied
+the patch, credit the reporter only. Add missing people to Individual
+Contributors and organizations to Corporate Sponsors.
+
+## Place
+
+During development, use the top unreleased section and its existing category.
+If the section says `These are only changes since ...`, add only later changes.
+During release prep, the former top section remains valid if it was unreleased at
+the target base ref. Do not rewrite the first line of a released bullet without
+the release manager's request.
+
+## Release Prep
+
+Before tagging:
+
+1. Set the release date.
+2. Compare `NEWS` with Git history and the Trac milestone.
+3. Check version and dependency text.
+4. Fix categories; merge or remove small internal notes.
+5. Update `doc/release_notes.xml` with curated release notes.
+
+Dates containing `x` are placeholders. Numeric dates must not be future dates and
+must be in descending order. After release, add the next development section at
+the top.
+
+## Checks
+
+Configured tree:
+
+```sh
+make check-news
+make check-contributor-credits
+```
+
+Unconfigured tree:
+
+```sh
+python3 -B utils/docs/tests/test_check_news.py
+sh utils/docs/check_news.sh .
+python3 -B utils/docs/tests/test_check_contributor_credits.py
+python3 -B utils/docs/check_contributor_credits.py --repo .
+```
+
+For a PR base-ref check:
+
+```sh
+utils/docs/check_news.sh --base-ref=origin/master .
+```
+
+The checker allows new bullets only in the current top unreleased section, or in
+the former top section when it was unreleased at the base ref.
+
+## Backpatch
+
+For each target branch, check `Version.config` and the top `NEWS` section. Use
+similar wording across branches, changing release-specific facts. Stable
+branches usually need bug-fix wording, not new-feature wording.

-----------------------------------------------------------------------

Summary of changes:
 doc/development/maintenance/_index.md | 11 +++--
 doc/development/maintenance/news.md   | 90 +++++++++++++++++++++++++++++++++++
 2 files changed, 97 insertions(+), 4 deletions(-)
 create mode 100644 doc/development/maintenance/news.md


hooks/post-receive
-- 
PostGIS
