From 4ab050d6f3c75089dc112b3a6176c27ec97173df Mon Sep 17 00:00:00 2001 From: Larry Knox Date: Fri, 31 Jan 2025 21:20:44 -0600 Subject: [PATCH] Remove unused NEWSLETTER files. --- release_docs/NEWSLETTER.txt | 18 ------------------ release_docs/NEWSLETTER_README.txt | 25 ------------------------- 2 files changed, 43 deletions(-) delete mode 100644 release_docs/NEWSLETTER.txt delete mode 100644 release_docs/NEWSLETTER_README.txt diff --git a/release_docs/NEWSLETTER.txt b/release_docs/NEWSLETTER.txt deleted file mode 100644 index acad5da773e..00000000000 --- a/release_docs/NEWSLETTER.txt +++ /dev/null @@ -1,18 +0,0 @@ -HDF5 version 1.14.6-1 currently under development - -Features included for the next major release: ----------------------------------------------------------------------------- - -* The release process now provides signed Windows and Mac installation binaries - in addition to the Debian and rpm installation binaries. The Mac binaries are - built as universal binaries on an ARM-based Mac. - -* Added new routines for interacting with error stacks: H5Epause_stack, - H5Eresume_stack, and H5Eis_paused. These routines can be used to indicate - that errors from a call to an HDF5 routine should not be pushed on to an error - stack. - ----------------------------------------------------------------------------- -Please see the full release notes for detailed information regarding this release, -including a detailed list of changes. - diff --git a/release_docs/NEWSLETTER_README.txt b/release_docs/NEWSLETTER_README.txt deleted file mode 100644 index f03f710d717..00000000000 --- a/release_docs/NEWSLETTER_README.txt +++ /dev/null @@ -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.