diff --git a/release_docs/RELEASE_PROCESS.md b/release_docs/RELEASE_PROCESS.md index 3208a2e48e5..266c87a4ecf 100644 --- a/release_docs/RELEASE_PROCESS.md +++ b/release_docs/RELEASE_PROCESS.md @@ -49,6 +49,7 @@ For more information on the HDF5 versioning and backward and forward compatibili 7. Review and update all INSTALL_* files in [release_docs][u4], if needed. - [INSTALL][u5] should be general info and not require extensive changes - [INSTALL_CMake.txt][u7] are the instructions for building under CMake. +8. Verify that [API Compatibility Macros][u13] are up to date for the release version. ### 4. Freeze Code (Release Manager | Test Automation Team) 1. Transition from performing maintenance on software to preparing for its delivery. @@ -57,7 +58,7 @@ For more information on the HDF5 versioning and backward and forward compatibili 3. Be sure to complete all four steps to update so numbers for each deployed lib file in the process described in config/lt_vers.am and check that the .so numbers for lib files in binaries correctly indicate compatibility status with the previous release. 4. Move all unresolved Milestone issues to the next release version in GitHub. 5. Verify that frozen code branch satisfies all existing regression test cases, and give the 'OK' to the release coordinator once all daily test configurations are passing as expected after the date of the code freeze. If there are failing tests after the code freeze date, coordinate with maintainers responsible for the failures to ensure that either the changes causing the failures are corrected or reverted. -6. Verify release branches for third-party software used: SZIP, ZLIB, and Plugins; and announce release versions to hdf5lib@hdfgroup.org. +6. Verify released versions (latest) of third-party software used: SZIP, ZLIB, and Plugins; and announce release versions to hdf5lib@hdfgroup.org. ### 5. Update Interface Version (Release Manager | Product Manager) 1. Verify interface additions, changes, and removals, and update the shared library interface version number. @@ -71,9 +72,11 @@ For more information on the HDF5 versioning and backward and forward compatibili 6. Confirm the necessity of and approve of any interface-breaking changes. If any changes need to be reverted, task the developer who made the change to do so as soon as possible. If a change is reverted, return to the previous step and regenerate the compatibility report after the changes is made. Otherwise, continue to the next step. 7. Update the .so version numbers in the [config/lt_vers.am][u9] file in the support branch according to [libtool's library interface version](https://www.gnu.org/software/libtool/manual/libtool.html#Versioning) scheme. - See [Updating version info (Libtool)](https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html#Updating-version-info) for rules to help update library version numbers. -8. After the release branch has been created, run `./autogen.sh` to regenerate build system files on the release branch and commit the changes. +8. After the release branch has been created, run bin/process_source.sh to regenerate the H5E header files on the release branch, and commit the changes. -### 6. Prepare Release Branch (Release Manager) +### 6. Verify that HDF5 library version has been updated from the previous release according to [HDF5 versioning policy][u16], consistent with semantic versioning rules. + +### 7. Prepare Release Branch (Release Manager) 1. Get the release branch ready for pre-release testing and packaging. 2. For all release preparation operations, the release coordinator will clone and push directly to canonical HDF5: - `$ git clone ​https://github.com/HDFGroup/hdf5.git` @@ -83,15 +86,15 @@ For more information on the HDF5 versioning and backward and forward compatibili - or create the new branch in GitHub GUI. 4. Check that required CMake files point to the specific versions of the third-party software (szip, zlib and plugins) that they depend on. - Update as needed. -5. Change the **support** branch to X.Y.{Z+1}-1 using the [bin/h5vers][u10] script: +5. Change the **support** branch to X.Y.{Z+1}-1 (\1) using the [bin/h5vers][u10] script: - `$ git checkout hdf5_X_Y` - `$ bin/h5vers -s X.Y.{Z+1}-1;` - `$ git commit -m "Updated support branch version number to X.Y.{Z+1}-1"` - `$ git push` -6. Change the **release preparation branch**'s version number to X.Y.Z-{SR+1} using the [bin/h5vers][u10]/bin/h5vers script: +6. Change the **release preparation branch**'s version number to X.Y.Z.1 using the [bin/h5vers][u10]/bin/h5vers script: - `$ git checkout hdf5_X_Y_Z;` - - `$ bin/h5vers -s X.Y.Z-{SR+1};` - - `$ git commit -m "Updated release preparation branch version number to X.Y.Z-{SR+1}"` + - `$ bin/h5vers -s X.Y.Z.1;` + - `$ git commit -m "Updated release preparation branch version number to X.Y.Z.1"` - `$ git push` 7. ** OBSOLETE CURRENTLY ** Update default configuration mode @@ -102,7 +105,7 @@ For more information on the HDF5 versioning and backward and forward compatibili ** END OBSOLETE CURRENTLY ** 8. E-mail hdf5lib@hdfgroup.org to indicate that the code freeze on the release support branch (i.e. hdf5_X_Y) has been lifted and development on the next maintenance release can resume. The code freeze will remain in place on the release preparation branch (i.e. hdf5_X_Y_Z) indefinitely. -### 7. Perform Release Testing (Test Automation Team | Release Manager | Project Leads) +### 8. Perform Release Testing (Test Automation Team | Release Manager | Project Leads) 1. Verify that source and binary distributions of HDF5 are acceptable on all target operating environments. 2. Create a page on Confluence as a sub-page of the current release version's project collaboration page (see HDF5 Maintenance Releases) to document release testing results. 3. Document the test procedure that will be used for this release on the new sub-page. @@ -110,9 +113,10 @@ For more information on the HDF5 versioning and backward and forward compatibili 5. Schedule and enable daily automated regression testing of the release preparation branch (i.e. hdf5_X_Y_Z). Give the 'OK' to proceed once all required tests have verified that HDF5 is functioning as intended on all target operating environments. 6. Select release build from workflow. 7. Choose the release branch -8. Change ‘Release version tag’ name to 'hdf5_X.Y.Z.P' - - P is some pre-release number. -9. Send a message to the HDF forum indicating that a pre-release source package is available for testing at /{hdf5-X.Y.Z-P}> and that feedback from the user community on their test results is being accepted. +8. Change ‘Release version tag’ name to 'X.Y.Z.P' + - P is a pre-release number, starting at 1 for first pre-release. + This will create a new tag 'vX.Y.Z.P'. The tag for the final release will be 'vX.Y.Z' +9. Send a message to the HDF forum indicating that a pre-release source package is available for testing at /{hdf5-X.Y.Z.P}> and that feedback from the user community on their test results is being accepted. 10. Contact paying clients who are interested in testing the pre-release source package and inform them that it is available for testing and that feedback on their test results of the pre-release is appreciated. 11. This should be automated and currently github binaries are not signed. - Follow the [How to sign binaries with digital certificates(this is missing)]() work instructions to sign each Windows and Mac binary package with a digital certificate. @@ -164,7 +168,7 @@ For more information on the HDF5 versioning and backward and forward compatibili 19. Decide if another cycle of pre-release testing should occur based on the issue reports received and the actions taken during this cycle. If another round of testing is required (i.e. there were significant issues in pre-release testing which resulted in code changes), increment the subrelease version number and go back to step 7.2. If no further testing is required (i.e. no code changes were made and issues were documented as known issues, or code changes were trivial, unit tested, and exhaustive testing is unneeded), then proceed. -### 8. Finalize Release Notes (Release Manager) +### 9. Finalize Release Notes (Release Manager) 1. Perform a final review of release notes and ensure that any new changes made to the source, any new known issues discovered, and any additional tests run since the code freeze have been reflected in CHANGELOG.md and other appropriate in-source documentation files (INSTALL_*, etc.). (Refer to the sub-steps of step 3 for what to check). 2. Update the [CHANGELOG.md][u1] in the **support** branch (i.e. hdf5_X_Y) to remove entries in “Bugs fixed” and “New Features” sections and increment the version number for the following release (“Bug fixes since X.Y.Z” - occurs twice). - `$ git checkout hdf5_X_Y` @@ -173,7 +177,7 @@ For more information on the HDF5 versioning and backward and forward compatibili - `$ git push` 3. Update Release Notes in **release** branch (Release Manager) -### 9. Package and Distribute Release (Release Manager) +### 10. Package and Distribute Release (Release Manager) 1. h5vers could run genparser, which can change the generated files if certain code files have been changed since the files generated by genparser were committed on the release branch. This should be checked by running `git status --ignored;`, then running genparser, then repeating `git status --ignored;`. If there are modified files from either git status command, they should be committed (or deleted if there are backup files or an autom4te.cache directory), and at least minimal testing should be done to see that the software is still good with the changes. 2. Set version for release, removing the subrelease string, initially `$ bin/h5vers -s X.Y.Z;`. Any subsequent patch releases will need the subrelease number. 3. Run `bin/release` (similar to 8.2) and commit all the changed files. @@ -192,9 +196,9 @@ For more information on the HDF5 versioning and backward and forward compatibili - Press "Run Workflow" 8. Release hdf5_plugins following the same steps. -### 10. Add the contents of the CHANGELOG.md file in the release code to the HISTORY-X_Y file in the **support** branch, just below the introductory lines at the top of the HISTORY file. +### 11. Add the contents of the CHANGELOG.md file in the release code to the HISTORY-X_Y file in the **support** branch, just below the introductory lines at the top of the HISTORY file. -### 11. Conduct Release Retrospective (Release Manager) +### 12. Conduct Release Retrospective (Release Manager) 1. Schedule time and solicit comments from retrospective 2. Identify issues and document them @@ -212,3 +216,4 @@ For more information on the HDF5 versioning and backward and forward compatibili [u13]: https://support.hdfgroup.org/documentation/hdf5/latest/api-compat-macros.html [u14]: https://github.com/HDFGroup/hdf5/releases/tag/snapshot-1.14 [u15]: https://github.com/HDFGroup/hdf5/releases/tag/snapshot +[u16]: https://github.com/HDFGroup/hdf5/wiki/HDF5-Version-Numbers-and-Branch-Strategy diff --git a/src/H5.c b/src/H5.c index 839edf76b55..f4d922d2de5 100644 --- a/src/H5.c +++ b/src/H5.c @@ -72,9 +72,14 @@ bool H5_PKG_INIT_VAR = false; /* Library Private Variables */ /*****************************/ -/* Library incompatible release versions, develop releases are incompatible by design */ -static const unsigned VERS_RELEASE_EXCEPTIONS[] = {0}; -static const unsigned VERS_RELEASE_EXCEPTIONS_SIZE = 1; +/* Library known incompatible minor versions; develop releases are incompatible + * by design. 999 is entered for testing an exception as a minor version that + * will never occur. Any released minor version found to be truly incompatible + * (this should never happen) should be added to the list with 999. 999 alone + * in the list indicates that there are no incompatible minor versions. */ +static const unsigned VERS_MINOR_EXCEPTIONS[] = {999}; +/* The size should be set to the number of minor version exceptions in the list. */ +static const unsigned VERS_MINOR_EXCEPTIONS_SIZE = 1; /* Library init / term status (global) */ bool H5_libinit_g = false; /* Library hasn't been initialized */ @@ -806,8 +811,8 @@ H5get_libversion(unsigned *majnum /*out*/, unsigned *minnum /*out*/, unsigned *r * version numbers compiled into the library. * * Within major.minor.release version, the expectation - * is that all release versions are compatible, exceptions to - * this rule must be added to the VERS_RELEASE_EXCEPTIONS list. + * is that all minor versions are compatible, exceptions to + * this rule must be added to the VERS_MINOR_EXCEPTIONS list. * * Return: Success: SUCCEED * Failure: abort() @@ -823,8 +828,8 @@ H5get_libversion(unsigned *majnum /*out*/, unsigned *minnum /*out*/, unsigned *r "linked with a different version of static or shared HDF5 library.\n" \ "You should recompile the application or check your shared library related\n" \ "settings such as 'LD_LIBRARY_PATH'.\n" -#define RELEASE_MISMATCH_WARNING \ - "Warning! ***HDF5 library release mismatched error***\n" \ +#define MINOR_VERSION_MISMATCH_WARNING \ + "Warning! ***HDF5 library minor version mismatched error***\n" \ "The HDF5 header files used to compile this application are not compatible with\n" \ "the version used by the HDF5 library to which this application is linked.\n" \ "Data corruption or segmentation faults may occur if the application continues.\n" \ @@ -832,6 +837,15 @@ H5get_libversion(unsigned *majnum /*out*/, unsigned *minnum /*out*/, unsigned *r "linked with an incompatible version of static or shared HDF5 library.\n" \ "You should recompile the application or check your shared library related\n" \ "settings such as 'LD_LIBRARY_PATH'.\n" +#define MINOR_VERSION_FORWARD_COMPATIBLE_WARNING \ + "Warning! ***HDF5 library minor version forward compatibility error***\n" \ + "The HDF5 header files used to compile this application are from a newer\n" \ + "version of the HDF5 library than the one to which this application is linked.\n" \ + "Data corruption or segmentation faults may occur if the application continues.\n" \ + "This can happen when an application was compiled by a newer version of HDF5 but\n" \ + "linked with an older version of static or shared HDF5 library.\n" \ + "You should recompile the application or check your shared library related\n" \ + "settings such as 'LD_LIBRARY_PATH'.\n" static herr_t H5_check_version(unsigned majnum, unsigned minnum, unsigned relnum) @@ -841,8 +855,9 @@ H5_check_version(unsigned majnum, unsigned minnum, unsigned relnum) static bool checked = false; /* If we've already checked the version info */ static unsigned int disable_version_check = 0; /* Set if the version check should be disabled */ static const char *version_mismatch_warning = VERSION_MISMATCH_WARNING; - static const char *release_mismatch_warning = RELEASE_MISMATCH_WARNING; - herr_t ret_value = SUCCEED; /* Return value */ + static const char *minor_version_mismatch_warning = MINOR_VERSION_MISMATCH_WARNING; + static const char *minor_version_forward_compatible_warning = MINOR_VERSION_FORWARD_COMPATIBLE_WARNING; + herr_t ret_value = SUCCEED; /* Return value */ FUNC_ENTER_NOAPI_NOINIT_NOERR @@ -860,8 +875,8 @@ H5_check_version(unsigned majnum, unsigned minnum, unsigned relnum) disable_version_check = (unsigned int)strtol(s, NULL, 0); } - /* H5_VERS_MAJOR and H5_VERS_MINOR must match */ - if (H5_VERS_MAJOR != majnum || H5_VERS_MINOR != minnum) { + /* H5_VERS_MAJOR must match */ + if (H5_VERS_MAJOR != majnum) { switch (disable_version_check) { case 0: fprintf(stderr, "%s%s", version_mismatch_warning, @@ -896,17 +911,17 @@ H5_check_version(unsigned majnum, unsigned minnum, unsigned relnum) break; } /* end switch */ - } /* end if (H5_VERS_MAJOR != majnum || H5_VERS_MINOR != minnum) */ + } /* end if (H5_VERS_MAJOR != majnum) */ - /* H5_VERS_RELEASE should be compatible, we will only add checks for exceptions */ - /* Library develop release versions are incompatible by design */ - if (H5_VERS_RELEASE != relnum) { - for (unsigned i = 0; i < VERS_RELEASE_EXCEPTIONS_SIZE; i++) { + /* H5_VERS_MINOR should be compatible, we will only add checks for exceptions */ + /* Library develop minor versions are incompatible by design */ + if (H5_VERS_MINOR != minnum) { + for (unsigned i = 0; i < VERS_MINOR_EXCEPTIONS_SIZE; i++) { /* Check for incompatible headers or incompatible library */ - if (VERS_RELEASE_EXCEPTIONS[i] == relnum || VERS_RELEASE_EXCEPTIONS[i] == H5_VERS_RELEASE) { + if (VERS_MINOR_EXCEPTIONS[i] == minnum || VERS_MINOR_EXCEPTIONS[i] == H5_VERS_MINOR) { switch (disable_version_check) { case 0: - fprintf(stderr, "%s%s", release_mismatch_warning, + fprintf(stderr, "%s%s", minor_version_mismatch_warning, "You can, at your own risk, disable this warning by setting the environment\n" "variable 'HDF5_DISABLE_VERSION_CHECK' to a value of '1'.\n" "Setting it to 2 or higher will suppress the warning messages totally.\n"); @@ -924,7 +939,7 @@ H5_check_version(unsigned majnum, unsigned minnum, unsigned relnum) "%s'HDF5_DISABLE_VERSION_CHECK' " "environment variable is set to %d, application will\n" "continue at your own risk.\n", - release_mismatch_warning, disable_version_check); + minor_version_mismatch_warning, disable_version_check); /* Mention the versions we are referring to */ fprintf(stderr, "Headers are %u.%u.%u, library is %u.%u.%u\n", majnum, minnum, relnum, (unsigned)H5_VERS_MAJOR, (unsigned)H5_VERS_MINOR, (unsigned)H5_VERS_RELEASE); @@ -938,7 +953,40 @@ H5_check_version(unsigned majnum, unsigned minnum, unsigned relnum) } /* end for */ - } /* end if (H5_VERS_RELEASE != relnum) */ + /* Check for forward compatibility usage. */ + if (H5_VERS_MINOR > minnum) { + switch (disable_version_check) { + case 0: + fprintf(stderr, "%s%s", minor_version_forward_compatible_warning, + "You can, at your own risk, disable this warning by setting the environment\n" + "variable 'HDF5_DISABLE_VERSION_CHECK' to a value of '1'.\n" + "Setting it to 2 or higher will suppress the warning messages totally.\n"); + /* Mention the versions we are referring to */ + fprintf(stderr, "Headers are %u.%u.%u, library is %u.%u.%u\n", majnum, minnum, relnum, + (unsigned)H5_VERS_MAJOR, (unsigned)H5_VERS_MINOR, (unsigned)H5_VERS_RELEASE); + + /* Bail out now. */ + fputs("Bye...\n", stderr); + abort(); + case 1: + /* continue with a warning */ + /* Note that the warning message is embedded in the format string.*/ + fprintf(stderr, + "%s'HDF5_DISABLE_VERSION_CHECK' " + "environment variable is set to %d, application will\n" + "continue at your own risk.\n", + minor_version_forward_compatible_warning, disable_version_check); + /* Mention the versions we are referring to */ + fprintf(stderr, "Headers are %u.%u.%u, library is %u.%u.%u\n", majnum, minnum, relnum, + (unsigned)H5_VERS_MAJOR, (unsigned)H5_VERS_MINOR, (unsigned)H5_VERS_RELEASE); + break; + default: + /* 2 or higher: continue silently */ + break; + } /* end switch */ + } + + } /* end if (H5_VERS_MINOR != minnum) */ /* Indicate that the version check has been performed */ checked = true; diff --git a/test/CMakeTests.cmake b/test/CMakeTests.cmake index 21b75f1f40b..8025d73b99c 100644 --- a/test/CMakeTests.cmake +++ b/test/CMakeTests.cmake @@ -654,6 +654,8 @@ set_tests_properties (H5TEST-tcheck_version-major PROPERTIES if ("H5TEST-tcheck_version-major" MATCHES "${HDF5_DISABLE_TESTS_REGEX}") set_tests_properties (H5TEST-tcheck_version-major PROPERTIES DISABLED true) endif () +# The minor version test will test version 999 and always fail because it's listed in +# VERS_MINOR_EXCEPTIONS. With WILL_FAIL "true" the failing test passes. add_test (NAME H5TEST-tcheck_version-minor COMMAND $ "-tm") set_tests_properties (H5TEST-tcheck_version-minor PROPERTIES WORKING_DIRECTORY ${HDF5_TEST_BINARY_DIR}/H5TEST @@ -663,13 +665,12 @@ set_tests_properties (H5TEST-tcheck_version-minor PROPERTIES if ("H5TEST-tcheck_version-minor" MATCHES "${HDF5_DISABLE_TESTS_REGEX}") set_tests_properties (H5TEST-tcheck_version-minor PROPERTIES DISABLED true) endif () -# release + 1 should pass on non-develop branches +# release + 1 should always pass (not checked) add_test (NAME H5TEST-tcheck_version-release COMMAND $ "-tr") set_tests_properties (H5TEST-tcheck_version-release PROPERTIES WORKING_DIRECTORY ${HDF5_TEST_BINARY_DIR}/H5TEST ENVIRONMENT "${CROSSCOMPILING_PATH}" - WILL_FAIL "true" -) +) if ("H5TEST-tcheck_version-release" MATCHES "${HDF5_DISABLE_TESTS_REGEX}") set_tests_properties (H5TEST-tcheck_version-release PROPERTIES DISABLED true) endif () diff --git a/test/tcheck_version.c b/test/tcheck_version.c index 89601b741dc..5564818e1cf 100644 --- a/test/tcheck_version.c +++ b/test/tcheck_version.c @@ -70,7 +70,7 @@ parse(int ac, char **av) major++; break; case 'm': - minor++; + minor = 999; break; case 'r': release++;