Skip to content
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

Clarification of versioning procedures #2619

Closed
pulkomandy opened this issue May 22, 2024 · 2 comments
Closed

Clarification of versioning procedures #2619

pulkomandy opened this issue May 22, 2024 · 2 comments
Assignees

Comments

@pulkomandy
Copy link

pulkomandy commented May 22, 2024

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 (09d4e9c), after the version was changed to 1.13.0 (518d426).

The tagging after the version update does not seem to match the documented release process from the README:

July 9, 2020: A new LTS release occurs. A new release is created, the version remains 1.9.0, and the LTS release is tagged LTS_07_2020. The main branch bumps to 1.10.0 and is tagged 1.10.0.

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.

@ewertons
Copy link
Contributor

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.

@ewertons
Copy link
Contributor

Tag LTS_03_2024 has been changed from 09d4e9c to 86e81e9.

Thanks @pulkomandy , and sorry again for disrupting your integration system.
We also updated our jobs to avoid this in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants