[geos-commits] [SCM] GEOS branch main updated. 0fb228d14f7d03e5d82794ee4a31e6b413e0ab10

[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 "GEOS".

The branch, main has been updated
       via  0fb228d14f7d03e5d82794ee4a31e6b413e0ab10 (commit)
      from  80b76d6fdbd29442e5a5562f859be78807f2884a (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 0fb228d14f7d03e5d82794ee4a31e6b413e0ab10
Author: Martin Davis <mtnclimb at gmail.com>
Date:   Thu May 23 20:30:58 2024 -0700

    Update DEVELOPER-NOTES.md

diff --git a/DEVELOPER-NOTES.md b/DEVELOPER-NOTES.md
index 79f6743ca..ec1ed13e0 100644
--- a/DEVELOPER-NOTES.md
+++ b/DEVELOPER-NOTES.md
@@ -7,9 +7,9 @@
   * Having various visual tooling, JTS is an easier platform to debug spatial algorithms in.
   * Being Java, JTS has less language legacy than GEOS, which was originally ported when STL was not part of the standard, and therefore reflects a mix of styles and eras.
 
-* Ideally, new algorithms will be implemented in JTS and then ported to GEOS.
-* Smaller performance optimizations in GEOS can travel back to JTS.
-
+* Ideally, new algorithms are implemented in JTS and then ported to GEOS.
+  * Sometimes GEOS gains new functionality; ideally this is backported to JTS
+* Performance optimizations in GEOS can backport to JTS.
   * Short circuits, indexes, other non-language optimizations, should be ticketed in JTS when they are added to GEOS.
 
 ### Follow JTS as Much as Possible

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

Summary of changes:
 DEVELOPER-NOTES.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
GEOS