-
-
Notifications
You must be signed in to change notification settings - Fork 290
HDF5 Version Numbers and Branch Strategy
Dana Robinson edited this page Oct 23, 2024
·
12 revisions
Starting with HDF5 2.0, develop will have a version number equal to the next major release. We will no longer skip odd numbers.
- develop will continue to be the main development trunk
- v2.x, etc. will be the maintenance branch (like hdf5_1_14)
- Created just before a major release
- Kept in sync with develop
- Only one v#.x branch will be alive at one time
- No longer maintained when the next release will be a major release (so there will be a 'maintenance holiday' between now and the 2.0.0 release)
- v2.0, v2.1 etc. will be release branches (like hdf5_1_14_5)
- Created shortly before a release
- Kept in sync with the parent maintenance branch until the release happens
- Tags are created from this branch when we release
- Patch releases will be created by cherry picking bugfixes into this branch and creating a new release tag
- Can be kept around for posterity
Tags for released versions will be named v<major>.<minor>.<patch>. We will keep old tags around for posterity, but will also create new tags for all released versions of HDF5 that use the vx.y.z scheme.