-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to bump main branch libfabric version #8904
Comments
Yes, we can update the version in preparation for the next release. |
Does that mean the version in main branch is always lower than released branch before preparing a release? That sounds odd to me. The bug in #8826 is that So we either need to add a FI_VERSION check in https://github.com/ofiwg/libfabric/blob/main/prov/efa/src/efa_mr.c#L268, which is done in #8902, Which solution do you prefer? I would prefer the latter one as having a main branch of version 1.18* is kind of strange. |
We updated the main branch to v1.18.0rc1, then created the v1.18.x branch. The main branch simply hasn't been updated with a new version since then. Updating the defines is trivial and can be done. Updating the version in configure.ac is less trivial and either means waiting closer to the actual release or predicting whether there will be any changes in the public header files. |
I see, I think we should have updated the version as part of this PR 49d1a76, which changed the public header files. |
Should we update the version to 1.19.0 or 1.19.0rc1? It looks to me 1.19.0rc1 makes |
The version should be MAJOR 1, MINOR 19, REVISION 0. rc1 is a package number and part of configure.ac. |
Btw, don't update configure to rc1. You can update to a1 if needed, but I usually update configure as part of the release process. |
I see, so I can just bump this line https://github.com/ofiwg/libfabric/blob/main/include/rdma/fabric.h#L87, is that good for you? |
PR is merged |
https://github.com/ofiwg/libfabric/blob/main/configure.ac#L11
Should it be updated to 1.19.0 or newer? I am asking because I was seeing a bug caused by this PR #8826 which only populate
hmem_data
for FI_VERSION >= 1.19, but the current libfabric version is 1.18.0rc1, which is even lower than the v1.18.x branch.The text was updated successfully, but these errors were encountered: