Stage for v2.5.18.0

Signed-off-by: Larry Gritz <lg@larrygritz.com>

CHANGES.md

@@ -1,6 +1,13 @@
-Release 2.5.18.0 (? 2024) -- compared to 2.5.17.0
+Release 2.5.18.0 (Jan 1, 2025) -- compared to 2.5.17.0
 --------------------------------------------------------
-
+- *exr*: Avoid integer overflow for large deep exr slice strides [#4542](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/4542)
+- *pnm*: Broken pnm files with invalid resolution [#4561](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/4561)
+- *build*: Use target_compile_options (fixes a LibRaw build issue) [#4556](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/4556) (by Don Olmstead)
+- *testing*: Add new ref output for libheif updates [#4525](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/4525)
+- *ci*: Increased the macos timeout slightly to fix spurious failures [#4526](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/4526)
+- *ci*: Fix broken CI for ASWF 2021 and 2022 containers [#4543](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/4543)
+- *docs*: Clarify 'copy_image' example [#4522](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/4522)
+- *docs*: Update some old links to our new vanity URLs [#4533](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/4533)
 
 
 Release 2.5.17.0 (Nov 1, 2024) -- compared to 2.5.16.0
@@ -32,7 +39,6 @@ Release 2.5.16.0 (Oct 1, 2024) -- compared to 2.5.15.0
 - *admin*: Change docs and comments references master -> main [#4435](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/4435)
 
 
-
 Release 2.5.15.0 (Sep 1, 2024) -- compared to 2.5.14.0
 --------------------------------------------------------
 - *ffmpeg*: Add proper detection of new FFmpeg versions [#4394](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/4394) (by Darby Johnston)

RELEASING.md

@@ -369,12 +369,13 @@ having CC prefixes in as many commit messages possible helps make the release
 notes process be simpler and more automated.
 
 We have been using the [git-cliff](https://github.com/orhun/git-cliff) tool
-as the starting point for relese notes. The command we use is:
+as the starting point for release notes. The command we use is:
 
-    git cliff -c src/doc/cliff.toml -d v1.2.3.4..HEAD > cliff.out.md
+    git cliff -c src/doc/cliff.toml release..dev-2.5 > cliff.out.md
 
-where v1.2.3.4 in this example is the tag of the last release. You could also
-use commit hashes to denote the range of changes you want to document.
+to capture the changes from the last release to the current tip of the dev-2.5
+staging branch. You could also use commit hashes to denote the range of
+changes you want to document.
 
 **For monthly patch releases**