New tag / version

[Fl-Al-Ve]

Hi,

I have noticed, that the last tag in this repository is from 2020.
Since then some changes and improvements have happend in the main/development branch.

Would it be possible to create a new tag in the near future?
Referring to a fixed tag is way better (and easier) to argument than just some "random commit ID".

I would really like to hear your opinion on this.

Kind regards.

[obgm]

I concur! 👍

[boaks]

AFAIK there is also a request from @mrdeep1 about a better version.h concept. Not sure, if that was low hanging fruit or more complex. But I guess, such a version.h in sync with tags will be needed.

[mrdeep1]

Sorry - mental blank about a better version.h, and I cant find reference to it.

[boaks]

I was also not able to find that in my mails. But you requested something to depend on when compiling against tinydtls e.g. when changing the API.

[boaks]

Found it, issue 143 - Issues for general cleanup?

[mrdeep1]

Thanks for finding it. Yes, whenever there is a public API change, having a different version number in PACKAGE_VERSION certainly helps when dynamically linking. In a similar vein, the libtinydtls.so file needs to be soft linked to a versioned version (e.g. libtinydtls.so.1.0.1) where the versioning rules are defined by https://autotools.info/libtool/version.html . libcoap's configure.ac shows how to do this. Note that the package version and .so version are unlikely to ever be the same.