So I am new to Go and upon developing some things I am curious about best practices for building/releasing libraries which will be used by other programs in Go.
Coming from a Java world, when you build a library, you build an actual artifact, thus having a separate process for testing + building + releasing a library makes sense. However in Go a library is just code living in a repository. The way I see it a release of a library in go consists of something like tagging a vcs repository or merging code to master branch or both. Should I make a Makefile (or whatever people use) for a library for running tests + build before doing a release even though I'm not actually creating a build artifact out of anything? Or should I run the library tests when building each application that uses it (Which feels very strange and wrong)? What are people doing out there? Any feedback on the matter would be welcome -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
