Scot Breitenfeld 1fc781961d Add change-request and manually-added-CODEOWNER lines to review checklist (#6528)
* Add change-request and manually-added-CODEOWNER lines to review checklist

Reviewers who request changes now get their own line under each area
their inline comments touch, whether or not they're a CODEOWNER or a
requested reviewer. CODEOWNERS who are review-requested directly by a
human (rather than auto-picked) get a separate required-approval line,
and their approval is now required for that area's sign-off in addition
to the usual reviewer's.

* Prune reviewers whose area dropped out of scope

A CODEOWNER requested for an area the PR used to touch, before a later
push narrowed the diff, was never removed: touchedAreaOwners only
reflects areas touched right now, so none of the existing avalanche
pruning ever considered them. Reproduced live on PR #6528, where the
branch's diff shrank to just .github/ but gheber/fortnern/mattjala
(owners of unrelated areas) stayed as requested reviewers.

Manually-added CODEOWNERS are exempt, since a human's deliberate
request shouldn't be silently undone by a later push.

* review-checklist: fix avalanche exemption regressing genuine avalanches

#6524 exempted a review_requested login's whole area from avalanche
detection to stop a manual re-request from being undone. But a genuine
CODEOWNERS avalanche's own review_requested sub-events look identical
to that case, and one of them can survive the ready_for_review vs.
review_requested concurrency race (#6530: draft PR marked ready for
review left all 3 CODEOWNERS owners requested instead of pruning to
one, because the surviving run's action was one of the avalanche's own
review_requested events, exempting the whole area).

Replace the exemption with a forced pick: the directly-requested login
still always survives, but now by replacing the rest of that area's
avalanche instead of exempting the area from pruning — so a genuine
avalanche still collapses to one person. Also gate justRequestedLogin
on !isBotSender, matching updatedManuallyAdded's existing reasoning
just above it: the bot's own requestReviewers calls fire this same
event and aren't a human decision.
2026-07-16 11:23:26 -05:00
2025-10-06 16:35:59 -05:00
2026-07-13 20:41:48 -05:00
2026-01-21 23:02:49 -06:00
2024-05-23 16:44:33 -05:00

HDF5 Logo

BSD DOI MIME Type develop cmake build status OpenSSF Best Practices


What is HDF5?

This repository contains a high-performance library's source code and a file format specification that implements the HDF5® data model. The model has been adopted across many industries, and this implementation has become a de facto data management standard in science, engineering, and research communities worldwide.

The HDF Group is the developer, maintainer, and steward of HDF5 software. Find more information about The HDF Group, the HDF5 Community, and other HDF5 software projects, tools, and services at The HDF Group's website.

Quick Start

  • New to HDF5? Start with the INSTALL.md guide for compilation and installation instructions.

  • Ready to build? See INSTALL_CMake.md for CMake-based builds.

  • Running on HPC? Check out README_HPC.md for parallel HDF5 configuration.

Table of Contents

Documentation

Documentation for all HDF software is available at:

See the CHANGELOG.md file in the release_docs/ directory for information specific to the features and updates included in this release of the library.

Platform-Specific Guides

Several files in the docs/ directory provide platform-specific details:

File Description
INSTALL General compilation and installation instructions (start here)
INSTALL_CMake.md Building with CMake
README_HPC.md Building and configuring Parallel HDF5 on HPC systems
INSTALL_Windows.md Windows installation
INSTALL_Cygwin.md Cygwin installation
USING_HDF5_CMake.md Building HDF5 applications with CMake
USING_CMake_Examples.md Building and testing HDF5 examples with CMake

Help and Support

The HDF Group staffs a free Help Desk accessible at https://help.hdfgroup.org and also monitors the Forum. Our free support service is community-based and handled as time allows. We'll do our best to respond to your question as soon as possible, but please note that response times may vary depending on the complexity of the issue and staff availability.

If you're interested in guaranteed response and resolution times, a dedicated technical account manager, and more benefits (all while supporting the open-source work of The HDF Group), please check out Priority Support.

Forum and News

The HDF Forum is provided for public announcements, technical questions, and discussions of interest to the general HDF5 Community.

These forums are provided as an open and public service for searching and reading. Posting requires completing a simple registration and allows one to join in the conversation. Please read the quickstart guide for more information on how to get started.

Release Schedule

HDF5 release schedule

HDF5 does not follow a regular release schedule. Instead, updates are based on the introduction of new features and the resolution of bugs. However, we aim to have at least one annual release for each maintenance branch.

Release Progress

Critical Priority

High Priority

The badges above show the current progress of critical and high priority issues with colors that reflect completion status:

  • 🟢 Green (90%+): Readying for Deployment - most issues completed
  • 🟡 Yellow (60-89%): Nearing Completion - on track for release
  • 🟠 Orange (40-59%): In Development - attention needed
  • 🔴 Red (<40%): Initial Phase - significant issues remain

Click the badges to view the detailed project board with current release items.

Downloads and Source Code

Snapshots and Releases

HPC Testing Results

View HPC configure/build/test results on CDash

Java Maven Artifacts

HDF5 Java bindings and examples are available as Maven artifacts. For detailed usage instructions including dependency configuration, repository setup, and platform-specific builds, see HDF5Examples/JAVA/README-MAVEN.md.

Contributing

We welcome contributions to HDF5! Whether you're fixing bugs, adding features, or improving documentation, your help is appreciated.

How to Contribute

  1. Report Issues: Use our GitHub Issues to report bugs or request features
  2. Submit Pull Requests: Fork the repository, make your changes, and submit a PR
  3. Join Discussions: Participate in the HDF Forum

For detailed contribution guidelines, please contact us through the Help Desk.

How to Cite HDF5

If you use HDF5 in your research, please cite it. This repository includes a CITATION.cff file containing standard citation metadata.

Quick DOI: 10.5281/zenodo.17808558

Build Status

Click to expand detailed build status

Continuous Integration

HDF5 develop daily build status CVE regression OSS-Fuzz Status Link Checker Status

Integration Testing

HDF-EOS5 build status netCDF build status h5py build status

HDF5 filter plugins testing

HDF5 plugins testing

VOL and VFD Testing

HDF5 VOL connectors build status HDF5 VFD build status


S
Description
No description provided
Readme Cite this repository
966 MiB
Languages
C 76.4%
Java 9%
Fortran 5.2%
CMake 3.1%
HTML 2.2%
Other 4%