Creating a release/tag

[grische]

As this project is far beyond the original version, it might be helpful to have some kind of releases /git tags in place. The last release of the sourceforge version is v1.2.3 as far as I can see.

Assuming they did use SemVer, the next reasonable version would be a v1.3.0. In case the (user) API changed, it might even be worth doing a v2.0.0 release.

I am not sure if you are considering to do retroactive git tags (i.e. releases) to point out which versions of the code are the most stable ones?

[sbastrakov]

Thanks @grische , I believe we should indeed consider that.

[ax3l]

Good idea, we usually add a -crp suffix to indicate it's a fork. 1.3.0-crp seams legit.

But lets remove the Makefile and add some improved docs such as an updated README (#22) first.

[ax3l]

Ok, PR opened in #25

Nevertheless, before a release the CMakeLists.txt also deserves some modernization / love.