Library versioning
Closed this issue · 3 comments
romshark commented
It's kinda odd to see a cool library still not being versioned even though it seems to have been around for 5 years already and going through a decent evolution.
Please consider:
- Following semantic versioning
- Defining version tags in the releases section
- Recording a change log in both the releases section and a separate
CHANGELOG.mdfile
This would greatly improve the library user experience and the seriousness of the project by allowing the user to achieve reproducible builds when using dep for example.
Currently, there seems to be no guarantee on backward-compatibility so the current release would need to start with 0.1 according to semver, though if it's already production ready then start with 1.0 right away.
This issue is loosely related to #47
Pallinder commented
I agree, let's get this one done asap!
Pallinder commented
Looks like I'll have some time for this one. Will get to this before merging the PR:s