openvds+ linked sdapi version vs release tag
I would like to understand, what versions of seismic-store/sdapi are used to build openvds+ binaries, and if possible the reasoning behind it.
From quick glance at CMake/Fetch3rdPartyInBuild.cmake
across 2.X openvds versions/tags:
- 2.0.X - dms - 1e933303
- 2.1.X - dms - 98d59b27b5
- 2.2.X - dms - 98d59b27b5
- 2.3.X - dms - 3633f2030
- 2.4.X - dms - 3633f2030
-
release/0.14
- dms - 98d59b27b5 -
release/0.15
- dms - 3633f2030
whereas sdapi release tags, have the following sha commits:
-
release/0.14
- d96f1e9b9806486e523ac4d9ea74a124af7ee68d -
release/0.15
- 04d68a061c3311c041d0ace4c222880032172065
it seems openVDS version tagged as release/0.14
is missing 35 commits (git rev-list d96f1e9b9 ^98d59b27b5 --pretty=oneline | wc -l
), from the same release tag release/0.14
on sdapi; and openVDS version tagged as release/0.15
is missing 5 commits on the corresponding release/0.15
(git rev-list 04d68a061c3311c041d0ace4c222880032172065 ^3633f2030 --pretty=oneline
).
I understand that those might not be "feature commits" irrelevant for the functionalities, but can we have some clarity on which seismic-store/sdapi version is supported in a given openVDS release?
Lastly, what is the desired flow of reporting issues emerging at sdapi level, when using openVDS SDK with a given OSDU DP release? Should the tickets be created for openVDS, or directly in sd-api repository with reference to openVDS version used?