Fixed versions/releases required instead of latest

[ndbg2024]

Hi Jonrosner,

I would like to kindly request fixed versions.
We would like to see some fixed versions/releases so that a particular version/release would have the same configurations which can be relied upon whenever its pulled up.

Hence, we would look forward to have some fixed versions/releases going forward.
Please do let us know if this can be a possibility and if yes, the timeline for the same as well.

Thanks.

[BF-Moritz]

Hi Jonrosner,

I can only aggre with ndbg2024. Versions would make a lot of things easier:

1. Make breaking changes avoidable. You said yourself, you will always be backwars compatible (Feature Request - versioning #131 (comment)) but looking at the issues here, I found at least one isntance with breaking changes (ODIC Callback #22 (comment))
2. I monitore my docker containers with the version. That is not possible with my current setup. I could check the hashes, but why the hassle? And then i dont know, if the update is just a small bugfix or we got new features.

So please ad versions or at least put the commit tag as the version.

Thanks.

[jonrosner]

Thanks for raising this issue. I didn't see the need for versioning before. But as this topic comes up a lot I will reevaluate it. I definitely won't use SemVer but using the git commit hash might be an option. I'd still encourage everybody to just stay on latest.

We would like to see some fixed versions/releases so that a particular version/release would have the same configurations which can be relied upon whenever its pulled up.

You can always rely on the configuration staying backwards compatible. I do take a lot of care to keep it this way. Updates should always be safe. If they are not then it is a mistake on my side that no versioning could have avoided.