Developer Pulling Mainline IMSDK with Older SDK Causes Mismatch

[shanmaju]

Issue summary

If developers continue using an older SDK but pull the latest mainline IMSDK code, it can lead to version mismatches between the SDK and sample/app code. This makes failures hard to diagnose and increases the debugging burden on the CE team. Therefore, there must be a clear, enforced mapping between each SDK release and the corresponding IMSDK code branch/commit, so developers always know which source revision is compatible with a given SDK version.

IMSDK working on branching, we would like to know, plan for SDK versioning

[ricardosalveti]

If all you are concerned with is the IMSDK versioning, then this needs to be raised at https://github.com/qualcomm/gst-plugins-imsdk.

Mainline is harder to keep track on as we often update the SDK in non-compatible ways, it will be stable once 2.0 is branched out, but then we need to make sure that IMSDK itself is not getting updated in non-compatible ways.