4 files changed, 59 insertions, 28 deletions
diff --git a/release_docs/INSTALL_CMake.txt b/release_docs/INSTALL_CMake.txt
index 4d4af24..94f525b 100644
--- a/release_docs/INSTALL_CMake.txt
+++ b/release_docs/INSTALL_CMake.txt
@@ -1104,7 +1104,7 @@ Using individual command presets (where <compiler-type> is  GNUC or MSVC or Clan
     cpack --preset ci-StdShar-<compiler-type>
 
 
-Using the workflow preset to configure, build, test and package the standard configuration is:
+Using the workflow preset to configure, build, test and package the standard configuration:
     change directory to the hdf5 source folder
     execute "cmake --workflow --preset ci-StdShar-<compiler-type> --fresh"
           where <compiler-type> is  GNUC or MSVC or Clang
diff --git a/release_docs/NEWSLETTER.txt b/release_docs/NEWSLETTER.txt
index f03f710..e69de29 100644
--- a/release_docs/NEWSLETTER.txt
+++ b/release_docs/NEWSLETTER.txt
@@ -1,25 +0,0 @@
-INTRODUCTION
-============
-
-This purpose of this document is to contain entries that can be used to quickly
-produce a release newsletter. When something is added to the library that is
-"newsletter worthy" (i.e., new feature, CVE fix, etc.) a summary note should
-be added here.
-
-The format should look like this:
-
-* SUMMARY OF NEWSLETTER-WORTHY THING
-
-    Here is where you describe the summary. Summarize the feature, fix, or
-    change in general language. Remember, RELEASE.txt is for communicating
-    technical specifics. Text entered here is more like advertising.
-
-    (GitHub #123, #125)
-
-The GitHub #s could be relevant issues or PRs. They will probably not appear
-in the final newsletter, but are so that the person writing the newsletter
-has easy access to context if they have questions.
-
-Every entry in RELEASE.txt does NOT require an entry here. The newsletter is
-for communicating major changes that are of interest to anyone. Minor bugfixes,
-memory leak fixes, etc. do not require entries.
diff --git a/release_docs/NEWSLETTER_README.txt b/release_docs/NEWSLETTER_README.txt
new file mode 100644
index 0000000..f03f710
--- /dev/null
+++ b/release_docs/NEWSLETTER_README.txt
@@ -0,0 +1,25 @@
+INTRODUCTION
+============
+
+This purpose of this document is to contain entries that can be used to quickly
+produce a release newsletter. When something is added to the library that is
+"newsletter worthy" (i.e., new feature, CVE fix, etc.) a summary note should
+be added here.
+
+The format should look like this:
+
+* SUMMARY OF NEWSLETTER-WORTHY THING
+
+    Here is where you describe the summary. Summarize the feature, fix, or
+    change in general language. Remember, RELEASE.txt is for communicating
+    technical specifics. Text entered here is more like advertising.
+
+    (GitHub #123, #125)
+
+The GitHub #s could be relevant issues or PRs. They will probably not appear
+in the final newsletter, but are so that the person writing the newsletter
+has easy access to context if they have questions.
+
+Every entry in RELEASE.txt does NOT require an entry here. The newsletter is
+for communicating major changes that are of interest to anyone. Minor bugfixes,
+memory leak fixes, etc. do not require entries.
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index 7330f4a..bb0448e 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -13,9 +13,9 @@ HDF5 source.
 Note that documentation in the links below will be updated at the time of each
 final release.
 
-Links to HDF5 documentation can be found on The HDF5 web page:
+Links to HDF5 documentation can be found on:
 
-     https://portal.hdfgroup.org/display/HDF5/HDF5
+     https://portal.hdfgroup.org/documentation/
 
 The official HDF5 releases can be obtained from:
 
@@ -47,6 +47,13 @@ New Features
 
     Configuration:
     -------------
+    - Deprecate bin/cmakehdf5 script
+
+      With the improvements made in CMake since version 3.23 and the addition
+      of CMake preset files, this script is no longer necessary.
+
+      See INSTALL_CMake.txt file, Section X: Using CMakePresets.json for compiling
+
     - Overhauled LFS support checks
 
       In 2024, we can assume that Large File Support (LFS) exists on all
@@ -640,6 +647,20 @@ Support for new platforms, languages and compilers
     
 Bug Fixes since HDF5-1.14.0 release
 ===================================
+    Configuration:
+    -------------
+    - Fix Autotools -Werror cleanup
+
+      The Autotools temporarily scrub -Werror(=whatever) from CFLAGS, etc.
+      so configure checks don't trip over warnings generated by configure
+      check programs. The sed line originally only scrubbed -Werror but not
+      -Werror=something, which would cause errors when the '=something' was
+      left behind in CFLAGS.
+
+      The sed line has been updated to handle -Werror=something lines.
+
+      Fixes one issue raised in #3872
+
     Library
     -------
     - Fixed a bug that causes the library to incorrectly identify
@@ -678,6 +699,13 @@ Bug Fixes since HDF5-1.14.0 release
       overflow. Rather than return positive infinity, the library would
       return truncated data. This has now been fixed.
 
+    - Fixed error when overwriting certain nested variable length types
+
+      Previously, when using a datatype that included a variable length type
+      within a compound or array within another variable length type, and
+      overwriting data with a shorter (top level) variable length sequence, an
+      error could occur. This has been fixed.
+
     - Fixed asserts raised by large values of H5Pset_est_link_info() parameters
 
       If large values for est_num_entries and/or est_name_len were passed
@@ -1641,6 +1669,9 @@ Known Problems
     in the HDF5 source. Please report any new problems found to
     help@hdfgroup.org.
 
+    File space may not be released when overwriting or deleting certain nested
+    variable length or reference types.
+
 
 CMake vs. Autotools installations
 =================================