@jingweno How far are we from a one-point-oh?

@pengwynn I'm using go-octokit in gh and the current design has been stable for a while, although not all API endpoints have been implemented. The current API, IMHO, is quite enjoyable to use.

I chatted with @technoweenie earlier though and we agree we should explore building a smarter hypermedia client with URL caching etc. That says potentially we'll break the current design in go-octokit. But we didn't come to a conclusion on how to move forward.

Ah, apologies if go-octokit isn't ready for getting listed, thought its absence was just an oversight. But cool, it its stable enough glad to prompt the discussion.

octokit.rb is actually the only official library which is currently >= 1.0.0. Both octokit.objc and octokit.net are < 1.0.0.

@jdennes: Go libraries are more strict about maintaining backwards compatibility because the import system lacks any real versioning. There are ways around it of course, but users of your library may have problems if you introduce breaking changes to master.

So really, once we add it to the list and start encouraging people to use go-octokit, it kind of has to be 1.0.

@technoweenie: 🆒 — closing this for now then.