Consider doing Github Releases/Tags with Semantic Versions

[solvingj]

It would be very helpful for package ecosystems and many other consumers who care enough about stability of their dependencies to need to pin them. Pinning to specific commits on the master branch is awkward. It is much more maintainable for consumers to have semantic versions on dependencies.

The CMakeLists.txt says the version is 1.1.0 and presumably this value gets updated from time-to-time when there's a significant change to the library. If the current commit is a "stable 1.1.0", please consider doing a Github release of a .tar.gz and/or .zip of the repository . It's trivial.

[YarikTH]

I like the library, even not yet used it. It has a lot of stars, it highly probably does exactly what I need, but the lack of releases is a big problem.
I don't use package managers, but I using submodules instead. But even for such usage, I want to use the latest stable version of the library. Without releases, I can't guess which one is stable.
And If I hit problems I wouldn't know to which version move. Several commits later in the hope it fixed? Several commits before in hope it wasn't yet bugged? How should I report problems? I use library version <git_hash_here>?