Draw attention to 3rd step in process to update so numbers for release. #4825
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lrknox
requested review from
derobins,
byrnHDF,
fortnern,
jhendersonHDF,
qkoziol,
vchoi-hdfgroup,
bmribler,
glennsong09,
mattjala and
brtnfld
as code owners
lrknox
added
Merge - To 1.14
Priority - 2. Medium ⏹
byrnHDF
approved these changes
Sep 12, 2024
hyoklee
requested changes
Sep 13, 2024
release_docs/RELEASE_PROCESS.md
Outdated
| 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 [email protected]. |
lrknox
commented
Sep 13, 2024
mattjala
approved these changes
Sep 13, 2024
hyoklee
approved these changes
Sep 13, 2024
lrknox
added a commit
to lrknox/hdf5
that referenced
this pull request
Sep 13, 2024
derobins
pushed a commit
that referenced
this pull request
Sep 16, 2024
* Convert exec_program to execute_process (#4819) * Fix a bug in Subfiling VFD vector I/O setup (#4821) Fixes a bug where the vector I/O sizes weren't being extended when one of the entries in the array is 0. This caused an over-read of the I/O sizes buffer and on some machines would cause a memory allocation failure due to the calculated I/O vector size being too large. * Add release note for signed binaries (#4826) * Draw attention to 3rd step in process to update so numbers for release. (#4825) * Update RESULT_VARIABLE
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resetting LT_VERS_AGE was missed for the last release. The 3rd step instruction is now clearly separated from the second step instruction and the steps are numbered. A step describing the update is also added to the RELEASE_PROCESS.md file.