Please start creating regular tags

[mwasilew]

When running tests in meta-qcom (or some other project) it should be possible to trace exact version of the test script that was used. At the moment we're using current tip of the tree when creating overlay in LAVA job. Please start tagging the sources regularly so we can move to a tagged version when creating an overlay.

[smuppand]

Thank you, @mwasilew, for putting together this requirement.

Since qcom-linux-testkit is consumed as a source snapshot for LAVA overlays, the main requirement is traceability/reproducibility rather than API compatibility. So CalVer-style tags are a better fit than SemVer initially.

Suggested policy:

• create annotated tags from main if it is green
• use tag format: testkit-YYYY.MM.DD
• create tags weekly, with optional ad-hoc tags for important fixes
• published tags should be immutable, do not force-move tags
• consumers such as meta-qcom/LAVA should use a configurable testkit ref, for example QCOM_LINUX_TESTKIT_REF=testkit-2026.04.24

[mwasilew]

Sounds like a plan!

[smuppand]

Sounds like a plan!

Yes.

Created the qcom-linux-testkit source snapshot tag:

 git ls-remote --tags origin "testkit-2026.04.24"
7a51bdcfa7ef431fb4207b7bf9d3ff2bf49a45f4        refs/tags/testkit-2026.04.24

This is an annotated tag from main and can be used by LAVA/meta-qcom overlay generation to pin an exact testkit source version instead of consuming the moving tip of main.