Release strategy
prepor opened this issue · comments
Hello.
For now documentation and code in clojars are inconsistent.
I think its good idea to have releases on breaking commits in master. Also, you can have "-SNAPSHOT" jars.
It'll make quiescent adoption more smooth.
Thank you!
Hi Prepor, just to clarify how I typically run projects:
There won't always be releases on breaking commits to master. Master is always use-at-your-own-risk, as are any snapshot releases (which you should feel free to build yourself). Versioned releases will be published whenever there is well tested, new functionality or bugfixes ready for end-users.
The mismatched documentation is an error and will be fixed for the next release.