Release notes for v2.5.2

[cary-ilm]

No description provided.

[lgritz]

Should "release notes" cull the PRs that are only about the repo itself or the CI, removing clutter so people scanning them will only see features or behavior changes that they might experience on their end?

[lgritz]

Merge cases I'd argue perhaps should be culled from release notes:

• TSC meeting minutes.
• Ephemeral changes, such as PRs that make a change that is reversed by a second PR within the same release cycle.
• Routine changes to the CI system (but do list truly notable changes, like informing people that a certain build configuration or new compiler version is now thoroughly tested, which was not before).

[lgritz]

LGTM, notwithstanding the procedural question I asked.

[cary-ilm]

I wondered the same thing, it does create clutter. I built the list with a script that just looks at all the PRs merged since the last release, but it's easy enough to cull them by hand.

…

On Thu, Jun 11, 2020 at 3:45 PM Larry Gritz ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In CHANGES.md <#756 (comment)> : > @@ -33,11 +35,92 @@ * [Version 1.0.1](#version-101) * [Version 1.0](#version-10) +## Version 2.5.2 (June 15, 2020) + +Patch release with various bug/security fixes and build/install fixes. + +### Summary + +* Invalid input could cause a heap-use-after-free error in DeepScanLineInputFile::DeepScanLineInputFile() +* Invalid chunkCount attributes could cause heap buffer overflow in getChunkOffsetTableSize() +* OpenEXRConfig.h now correctly sets OPENEXR_PACKAGE_STRING to "OpenEXR" (rather than "IlmBase") +* Various Windows build fixes + +### Merged Pull Requests + +* [755](#755) Fix OPENXR_PACKAGE_NAME +* [751](#751) Disable all Windows builds temporarily. Merge cases I'd argue perhaps should be culled from release notes: - TSC meeting minutes. - Ephemeral changes, such as PRs that make a change that is reversed by a second PR within the same release cycle. - Routine changes to the CI system (but do list truly notable changes, like informing people that a certain build configuration or new compiler version is now thoroughly tested, which was not before). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#756 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFC3DGLYSPZJRNRDY6SB7WLRWFNARANCNFSM4N3Z5VOA> .

-- Cary Phillips | R&D Supervisor | ILM | San Francisco