[SCM] postgis.net branch website updated. clarity-final-73-g68ca43d

[git at osgeo.org]

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.net".

The branch, website has been updated
       via  68ca43d194fe9e44f4ae16573ecb02085349e47d (commit)
      from  d4986c81100b5f0fe2a4e3e949b5228cd0abff9e (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 68ca43d194fe9e44f4ae16573ecb02085349e47d
Author: Regina Obe <lr at pcorp.us>
Date:   Sat Nov 18 03:50:05 2023 -0500

    minor update to trac putting in git ref

diff --git a/content/development/rfcs/rfc05.md b/content/development/rfcs/rfc05.md
index 949a6f8..5110088 100644
--- a/content/development/rfcs/rfc05.md
+++ b/content/development/rfcs/rfc05.md
@@ -51,7 +51,7 @@ The following are considered good source commit and tracking practices for the P
 
   1. Use meaningful descriptions for commit log entries. Format the git log to have a succint oneline description optionally followed by a detailed description after an empty line. Keep lines within 70 columns. Include trac ticket references in the detailed description. Ticket references will be signaled to trac so they can close tickets if "Closes #xxx" is found in the commit log or only result in comments if "References #xxx" is found. References to pull requests are better encoded as full links.
   2. We allow contributions via patches (on trac or via mailing lists) or pull requests from our primary or [CodeMirrors git mirrors](../../source_code).  If you are given a patch or pull request from a community person, make sure to keep their names in the commit log (`git commit --author "Name Surname <email>"`) and NEWS file. DO NOT USE the `MERGE` button on [CodeMirrors git mirrors](../../source_code) as mirrors will be overridden and the merged commit will be discarded; merge manually to official repo instead.
-  3. We use https://trac.osgeo.org/postgis for planning so make sure pending changes have tickets there so they are not overlooked when cutting releases. If you forget to add trac ticket references in a commit log, edit the trac ticket and put the notes in, such as "Fixed in master ..git hash and in branches/3.0 <githas>". The 'git/hash' character enables Trac to create a hyperlink from the ticket to the changeset.
+  3. We use https://trac.osgeo.org/postgis for planning so make sure pending changes have tickets there so they are not overlooked when cutting releases. If you forget to add trac ticket references in a commit log, edit the trac ticket and put the notes in, such as "Fixed in master ..git hash and in branches/3.0 <githas>". The 'hash/git' enables Trac to create a hyperlink from the ticket to the changeset.
   4. Make sure the NEWS file is updated in master branch for new features/breaking changes and in all the stable branches for bugfixes.
   5. Never commit new features to a stable branch without permission of the PSC or release manager. Normally only fixes should go into stable branches.
   6. New features go in the master branch.

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

Summary of changes:
 content/development/rfcs/rfc05.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
postgis.net