Make a release
Opened this issue · 4 comments
Hi!
Thank you for the great library.
I am interested in packaging your library for different C++ dependecy managers. But without release that's not so convinient (because in a recipe I must rely on specific commit instead of tag/release).
Can you please prepare any release of the library (v1.0 or whatever you want) for being more dependency_managers-friendly?
Thank you a lot!
Why would using 1.0 be better than a commit hash?
The advantage with a commit hash is that it is always automatically bumped when a bug is fixed. A version tag is something that I must bump manually, i.e., it is something that I might forget to do and thus screw up. I prefer having fewer things to screw up.
Library tag/release is required for packaging. Since all normal libraries provide to end users some version (usually semver) and user can rely on them. For packaging it's also useful since nowadays we lock on versions instead of commits.
Why version is better than commit hash - with version you can easily detect, which library version is older or newer, which has breaking changes, new patches, etc (semver provides such information).
According automatic updates: that's not really good idea since user usually wants specific version and want to get a control over bumping package version. Automatic updates don't work well since user can have different caching mechanisms in his build infra.
I hope my ideas are clear. So if it's not so difficult for you - can you please prepare a release of the library? :) If you choose semver - will be awesome.
Thank you a lot!
@zamazan4ik Quite late and maybe not exactly what you are looking for but maybe this helps: https://github.com/CodeFinder2/fast-cpp-csv-parser