Consider publishing through gopkg.in? about mgo HOT 5 CLOSED

@niemeyer I'm not having a dig - we're all very grateful for the time and effort that has gone into both mgo and gopkg.in - my comment was simply explaining there's little benefit for the added risk of relying on a 3rd party, regardless of whom that is.

Dom

from mgo.

Hi @kevinguard

I'm weary of using gopkg.in - it's maintained by the original mgo author and the mgo project was abandoned for a long time - I'd hate to see the same happen to gopkg.in and I'm not suggesting it will happen, but it's a risk for little reward.

The documentation is linked to from the README and we tag all releases to allow users to pin dependencies with a readable name. Is there something you'd like to see that gopkg.in provides?

Dom

from mgo.

@domodwyer Please don't extrapolate my lack of time to make changes in mgo into a strange territory. The mgo code never stopped working. In fact, it was good enough that you decided to use it, I think?

You are welcome.

from mgo.

No that was not your point, actually. There's a a direct reference to me personally.

You're welcome, Dom.

from mgo.

@domodwyer Appreciate your comment and thoughts. Totally agree! Thanks for keeping this repo great! Cheers!

from mgo.