Another thing along the same lines... "releasing a package" is really not something that requires effort for Go. There's no process... if the code is in github, it's released. A lot of the questions ask about difficulties in getting code from the maintainer to a consumer, but that just isn't a thing, since we have no central repository.
Also note that go packages don't have versions per se... so a lot of the version questions don't really apply. Some people do release new major "versions" of their packages, but it's effectively a completely different package, as far as the Go language is concerned. A lot of the questions were about what you do about breaking changes, and in Go, the mantra is "Don't make breaking changes." If you do, you make a new package (even if it's just foo.v2). I did my best with the survey, though it really needed a lot more options to pick "not applicable". :) -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
