/** \page rel_spec_114 Release Specific Information for HDF5 1.14
 *
 * Navigate back: \ref index "Main" / \ref release_specific_info
 * <hr>


\section sec_rel_spec_114 HDF5 Library and Tools 1.14.6

\subsection subsec_rel_info_114 Release Information

<table>
<tr>
<td style="background-color:#F5F5F5">
Version
</td>
<td>
HDF5 1.14.6
</td>
</tr>
<tr>
<td style="background-color:#F5F5F5">
Release Date
</td>
<td>
02/05/25
</td>
</tr>
<tr>
<td style="background-color:#F5F5F5">
Additional Release Information
</td>
<td>
<a href="https://\SRCURLALL/hdf5_1.14.6/release_docs/RELEASE.txt">RELEASE.txt</a>
</td>
</tr>
<tr>
<td style="background-color:#F5F5F5">
</td>
<td>
\ref sec_rel_spec_114_migrate
</td>
</tr>
<tr>
<td style="background-color:#F5F5F5">
</td>
<td>
\ref sec_rel_spec_114_change
</td>
</tr>
<tr>
<td style="background-color:#F5F5F5">
</td>
<td>
\ref sec_rel_spec_114_feat
</td>
</tr>
<tr>
<td style="background-color:#F5F5F5">
</td>
<td>
[Newsletter Announcement](https://www.hdfgroup.org/2025/02/05/release-of-hdf5-1-14-6-newsletter-205/)
</td>
</tr>
<tr>
<td style="background-color:#F5F5F5">
</td>
<td>
ABI/API compatibility reports between 1.14.6 and 1.14.5 [tar file](https://\RELURL/v1_14/v1_14_6/downloads/hdf5-1.14.6.html.abi.reports.tar.gz) or [individual html files](https://\RELURL/v1_14/v1_14_6/downloads/compat_report/index.html)
</td>
</tr>
<tr>
<td style="background-color:#F5F5F5">
</td>
<td>
[Doxygen generated Reference Manual](https://support.hdfgroup.org/documentation/hdf5/latest/)
</td>
</tr>
</table>


\subsection subsec_download_114 Downloads

Source code and binaries are available at:
<a href="https://\RELURL/v1_14/v1_14_6/downloads/index.html">https://support.hdfgroup.org/releases/hdf5/v1_14/v1_14_6</a>

Please refer to [Build instructions](https://\SRCURL/release_docs/INSTALL) for building with either CMake or Autotools.


\subsection subsec_obtain_method_114 Methods to obtain (gz file)

\li firefox – Download file and then run:  `gzip <distribution>.tar.gz | tar xzf -`
\li chrome –  Download file and then run:  `gzip -cd <distribution>.tar.gz | tar xvf -`
\li wget –
<div style="margin-left: 2em;">
    `wget https://github.com/HDFGroup/hdf5/releases/download/${PACKAGEVERSION}/<distribution>.tar.gz`<br>
    `gzip -cd <distribution>.tar.gz | tar xvf -`
</div>
\li `<distribution>` is hdf5-${PACKAGEVERSION}, where PACKAGEVERSION is 1.14.6 for this release


\subsection subsec_dox_gen_doc_114 Doxygen Generated Reference Manual

The new HDF5 documentation based on [Doxygen](https://www.doxygen.nl/index.html) is available \ref index "here".

This documentation is WORK-IN-PROGRESS.
Since this portion of the HDF5 documentation is now part of the source code, it gets the same treatment as code. In other words, issues, inaccuracies, corrections should be reported as issues in [GitHub](https://github.com/HDFGroup/hdf5/issues), and pull requests will be reviewed and accepted as any other code changes.

\section sec_rel_spec_114_migrate Migrating from HDF5 1.12 to HDF5 1.14
# Migrating to HDF5 1.14 from Previous Versions of HDF5

\subsection subsec_rel_spec_114_migrate_api API Changes
There are new API calls that require API Compatibility Macros in HDF5 1.14.0. There are, however,
two API calls which have had their signature change.

\subsection subsec_rel_spec_114_migrate_api_h5ireg H5Iregister_type / H5I_free_t
The signature of #H5Iregister_type did not change, but the #H5I_free_t callback it accepts did
have its signature change to add an asynchronous request parameter. There is no API compatibility
macro to paper over this change. The request parameter can be ignored in the callback if you are
not concerned with asynchronous operations and future IDs. A description of how the request
parameter should be used will be found in the (soon to be released) HDF5 Asynchronous Programming Guide.
\li <strong>Old:</strong> - <code>typedef herr_t (*H5I_free_t)(void *obj);</code>
\li <strong>New:</strong> - <code>typedef herr_t (*H5I_free_t)(void *obj, void **request);</code>

\subsubsection subsubsec_rel_spec_114_migrate_api_h5vlquery H5VLquery_optional
The way optional operations are handled in the virtual object layer (VOL) changed significantly in
HDF5 1.14.0. To better support this, the #H5VLquery_optional API call now takes an output flags
parameter instead of a Boolean. Since the entire 1.12 VOL API has been deprecated, no API
compatibility macro exists for this API call.
\li <strong>Old:</strong> - <code>herr_t H5VLquery_optional(hid_t obj_id, H5VL_subclass_t subcls, int opt_type, hbool_t *supported);</code>
\li <strong>New:</strong> - <code>herr_t H5VLquery_optional(hid_t obj_id, H5VL_subclass_t subcls, int opt_type, uint64_t *flags);</code>

\subsection subsec_rel_spec_114_migrate_vfl Virtual File Layer (VFL) Changes
The virtual file layer has changed in HDF5 1.14.0. Existing virtual file drivers (VFDs) will have
to be updated to work with this version of the library.

\subsection subsec_rel_spec_114_migrate_vol Virtual Object Layer (VOL) Changes
The virtual object layer has changed significantly in HDF5 1.14.0 and the 1.12 VOL API is now
considered deprecated and unsupported. Existing virtual object layer connectors should be updated
to work with this version of the library.

\section sec_rel_spec_114_feat New Features in HDF5 Release 1.14

The new features in the HDF5 1.14 series include:
\li \ref_rfc20240129<br />
    Support for the 16-bit floating-point \_Float16 C type has been added to
    HDF5. On platforms where this type is available, this can enable more
    efficient storage of floating-point data when an application doesn't
    need the precision of larger floating-point datatypes. It can also allow
    for improved performance when converting between 16-bit floating-point
    data and data of another HDF5 datatype.

\li \ref sec_async<br />
    HDF5 provides asynchronous APIs for the HDF5 VOL connectors that
    support asynchronous HDF5 operations using the HDF5 Event Set (H5ES)
    API. This allows I/O to proceed in the background while the application
    is performing other tasks.

\li \ref_rfc20200213<br />
    The basic idea behind sub-filing is to find the middle ground between
    single shared file and one file per process - thereby avoiding some
    of the complexity of one file per process, and minimizing the locking
    issues of a single shared file on a parallel file system.

\li \ref_rfc20200210<br />
    There is a desire to introduce and track modifications to an HDF5 file
    while preserving or having access to the file as it existed prior to a
    particular set of modifications. To this end, this RFC proposes an Onion
    Virtual File Driver (VFD) as an effectively in-file revision management
    facility. Users will be able to open a particular revision of the file,
    read from and make modifications to the file, and write to file as a new
    revision. The name "Onion" derives from a mnemonic: the original file
    exists with data layered atop one another from an original file to the
    most recent revision

\li \ref_rfc20120828<br />
    The HDF5 library allows a data access operation to access one dataset at
    a time, whether access is collective or independent. However, accessing
    multiple datasets will require the user to issue an I/O call for each
    dataset. This release provides a set of new routines that allow users
    to access multiple datasets with a single I/O call.

\li New tools h5dwalk and h5delete<br />
    The new tool h5dwalk provides parallelism for improved performance while
    also including critical logging capabilities to capture outputs from
    applying the serial tools over large collections of HDF5 files.

 
Note that the HDF5 Release 1.14.0 is the final released version of all the features
that were released in 1.13.0-1.13.3.

<h4>RFCs</h4>
\li \ref_rfc20240129
\li \ref sec_async
\li \ref_rfc20200213
\li \ref_rfc20200210
\li \ref_rfc20120828

\ref sec_rel_spec_114_change

 *
 * <hr>
 * Navigate back: \ref index "Main" / \ref release_specific_info
 *
*/
