Open Issues before release
faroit opened this issue · comments
I think #4 is fixed, we can make a public release and add more things later.
Shall we reset the version to 1.0.0 (it's on 1.3.0 currently)? I would keep it like this because it reflects the difference to our internal version.
In the future I would suggest that we increase the version number when we change the api, and write release notes so that users can better rely on a stable webmushra
+1/+1. I see it the same way
okay, so we start with 1.3.0
semantic versioning: if we fix things +0.0.1 if we break compatibility +0.1.0