Closed pulkomandy closed 5 months ago
Hi @pulkomandy , you are correct, there is an issue with the tagging for the last release. There was an automation cleanup done for the last LTS release and it caused this mistake, that's really unfortunate and we apologize for that. We will fix the tagging in a bit. Explicitly: LTS_03_2024 should result in azure-iot-sdk-c version 1.12.0, and main branch should be at 1.13.0 as of now.
Tag LTS_03_2024 has been changed from 09d4e9c to 86e81e94e813ceaf7a3d3ce57e83bfafc54a1269.
Thanks @pulkomandy , and sorry again for disrupting your integration system. We also updated our jobs to avoid this in the future.
Hello,
I don't understand the versioning for the latest LTS release.
In the latest tag: https://github.com/Azure/azure-iot-sdk-c/releases/tag/LTS_03_2024 it says "Code version: 1.12.0"
But in the git repository, the tag LTS_03_2024 is set at the same place as the tag 1.13.0 (09d4e9ca46d1facea7d6d0c7ac13e56edd0a715f), after the version was changed to 1.13.0 (518d426ac2a7b9afa3c03210a437d8c78f98a753).
The tagging after the version update does not seem to match the documented release process from the README:
Can you clarify which versioning is correct? Does LTS_03_2024 correspond to code version 1.12.0 or 1.13.0? What will be the version for the next release?
We are maintaining our own Debian packaging for Azure-SDK-C and we would like to make sure we use the correct version number.