Skip to content

Conversation

@loricooperhdf
Copy link
Contributor

@loricooperhdf loricooperhdf commented Oct 22, 2025

Cleaned up formatting, added links when available.

  • ✅ Added attribution language
  • @lrknox to do some organization (collect Cmake items, collect CVE fixes) IF time allows

@lrknox to help with organization
@brtnfld reminder to add attribution language


Important

Refined CHANGELOG.md with improved formatting, added section links, and enhanced navigation.

  • Formatting and Links:
    • Updated table of contents links in CHANGELOG.md for better navigation.
    • Added links to specific sections, e.g., bfloat16 predefined datatypes and complex numbers.
    • Changed macro EXTERNAL_HDF5_STATUS to lowercase for consistency.
    • Added backticks around code elements and paths for clarity.
  • Miscellaneous:
    • Fixed typos and improved consistency in language and formatting.
    • Added GitHub issue links for bug fixes and security issues.

This description was created by Ellipsis for b5ed0f1. You can customize this summary. It will automatically update as commits are pushed.

Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
byrnHDF
byrnHDF previously approved these changes Oct 23, 2025

Fixed GitHub issue [#4952](https://github.com/HDFGroup/hdf5/issues/4952)

### Fixed security issue CVE-2025-2310
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another CVE issue to be updated with a link. If that's the standard going forward, more of these CVE issues will probably appear in entry titles from currently unmerged PRs that don't yet list them this way.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was an editorial choice I made that perhaps I regret. Should I mention this to others to add the link? I can also keep an eye on this as code freeze approaches.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd say it's worth bringing up. We can also do a last editing pass near to the release as well.

@nbagha1 nbagha1 moved this from To be triaged to Scheduled/On-Deck in HDF5 - TRIAGE & TRACK Oct 30, 2025
lrknox
lrknox previously approved these changes Nov 3, 2025

## Acknowledgements:

We would like to thank the many HDF5 community members that contributed to HDF5 2.0.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"that" vs "who"?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can revisit your comments from this PR after we have a release branch.

The versions of `h5cc`, `h5fc`, `h5c++`, etc. generated by CMake were missing several options and features from the Autotools counterparts. Some of these options and features have now been implemented in the CMake versions, while some of them have not:
- The missing `--help`/`-h`, `-c`, `-echo`, and `-shlib`/`-noshlib` options have been implemented.
- The `-prefix` option was not implemented, as it didn't appear to function in the Autotools wrappers and is generally covered by pkg-config in the CMake wrappers.
- A new `-nohl` option has been added to avoid building and linking against the high-level HDF5 libraries if desired.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HDF5 libraries, if desired.


Note that support for a native FP8 datatype has not been added yet. This means that any datatype conversions to/from the new FP8 datatypes will be emulated in software rather than potentially using specialized hardware instructions. Until support for a native FP8 type is added, an application can avoid datatype conversion performance issues if it is sure that the datatype used for in-memory data buffers matches one of the above floating-point formats. In this case, the application can specify one of the above macros for both the file datatype when creating a dataset or attribute and the memory datatype when performing I/O on the dataset or attribute.

Also note that HDF5 currently has incomplete support for datatype conversions involving non-IEEE floating-point format datatypes. Refer to the 'Known Problems' section for information about datatype conversions with these new datatypes.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link to Known Problems section, perhaps?

@lrknox lrknox merged commit 1e66212 into HDFGroup:develop Nov 4, 2025
2 checks passed
@github-project-automation github-project-automation bot moved this from Scheduled/On-Deck to Done in HDF5 - TRIAGE & TRACK Nov 4, 2025
christian-wojek pushed a commit to christian-wojek/hdf5 that referenced this pull request Nov 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Component - Documentation Doxygen, markdown, etc.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants