From 93d6137d2363d8b03d9b2107b91960b89f731d79 Mon Sep 17 00:00:00 2001 From: Andrew Johnson Date: Mon, 15 Dec 2025 15:53:01 -0600 Subject: [PATCH] Add submodule release note entries --- documentation/new-notes/README.txt | 5 ++++- documentation/new-notes/normativeTypes-6.0.2.md | 7 +++++++ documentation/new-notes/pvAccess-7.1.8.md | 11 +++++++++++ documentation/new-notes/pvData-8.0.7.md | 11 +++++++++++ documentation/new-notes/pvaClient-4.8.1.md | 8 ++++++++ 5 files changed, 41 insertions(+), 1 deletion(-) create mode 100644 documentation/new-notes/normativeTypes-6.0.2.md create mode 100644 documentation/new-notes/pvAccess-7.1.8.md create mode 100644 documentation/new-notes/pvData-8.0.7.md create mode 100644 documentation/new-notes/pvaClient-4.8.1.md diff --git a/documentation/new-notes/README.txt b/documentation/new-notes/README.txt index e95f559af..f866e0ddc 100644 --- a/documentation/new-notes/README.txt +++ b/documentation/new-notes/README.txt @@ -34,7 +34,7 @@ where nnn is the number of the pull request. If you haven't created the pull request yet you can use the number from a related GitHub issue, or use some other name, then rename and push it after the PR has been created. -The file should start with a level-3 Markdown title for the entry, like this: +The file *must* start with a level-3 Markdown title for the entry, like this: ### Conflict-free release note entries for GitHub pull requests @@ -46,6 +46,9 @@ The file should start with a level-3 Markdown title for the entry, like this: (followed by a blank line to separate it from the next paragraph), or a link to the PR may be integrated into the text that follows. * Use blank lines between paragraphs of text, and code-blocks for examples. + * I recommend using [semantic line-breaks](https://sembr.org/) in Markdown + files, it makes editing easier and reduces the number of lines that change + in most commits. This README.txt file isn't formatted as Markdown. Release note entries are not intended to provide full documentation of major features. For small features or changes though, they may provide all the diff --git a/documentation/new-notes/normativeTypes-6.0.2.md b/documentation/new-notes/normativeTypes-6.0.2.md new file mode 100644 index 000000000..fb181c6f0 --- /dev/null +++ b/documentation/new-notes/normativeTypes-6.0.2.md @@ -0,0 +1,7 @@ +### normativeTypes Module + +Changes to this module since the previous release: + +#### Release 6.0.2 + +- Fix potential NULL pointer dereference in `NTNDArray::getValueSize()` diff --git a/documentation/new-notes/pvAccess-7.1.8.md b/documentation/new-notes/pvAccess-7.1.8.md new file mode 100644 index 000000000..2810e4c84 --- /dev/null +++ b/documentation/new-notes/pvAccess-7.1.8.md @@ -0,0 +1,11 @@ +### pvAccess Module + +Changes to this module since the previous release: + +#### Release 7.1.8 + +- Compatible changes + - Capped the number and age of PVA beacons to avoid a resource leak. Beacons + older than 360 seconds will be destroyed automatically, new beacons will be + ignored if >=2048 exist already. + - Various Clang, MSVC and GCC compiler warnings cleaned up. diff --git a/documentation/new-notes/pvData-8.0.7.md b/documentation/new-notes/pvData-8.0.7.md new file mode 100644 index 000000000..26ff0fec0 --- /dev/null +++ b/documentation/new-notes/pvData-8.0.7.md @@ -0,0 +1,11 @@ +### pvData Module + +Changes to this module since the previous release: + +#### Release 8.0.7 + +- Compatible changes + - Allow epics::pvData::Timer to be cancelled during callback execution. + - Clang compiler warnings cleaned up. + - Limit periodic timers to one catch-up after missing many events. + diff --git a/documentation/new-notes/pvaClient-4.8.1.md b/documentation/new-notes/pvaClient-4.8.1.md new file mode 100644 index 000000000..cf8916d36 --- /dev/null +++ b/documentation/new-notes/pvaClient-4.8.1.md @@ -0,0 +1,8 @@ +### pvaClient Module + +Changes to this module since the previous release: + +## Release 4.8.1 + +* Fix error message generation code. +