This is why we should make go get work on trunk

[Nate Finch]

(Resending since the list didn't like my screenshots)

https://twitter.com/beyang/statuses/474979306112704512

https://github.com/juju/juju/issues/43

Any tooling that exists for go projects is going to default to doing "go
get".  Developers at all familiar with go, are going to use go get.

People are going to do

go get github.com/juju/juju

and it's going to fail to build, and that's a terrible first impression.

Yes, we can update the README to tell people to run godeps after running go
get, and many people are not going to read it until after they get the
error building.

Here's my suggestion:

We make go get work on trunk and still use godeps (or whatever) for
repeatable builds of release branches.

There should never be a time when tip of trunk and all dependent repos
don't build.  This is exceedingly easy to avoid.

Go crypto (which I believe is what is failing above) is one of the few
repos we rely on that isn't directly controlled by us.  We should fork it
so we can control when it updates (since the people maintaining it seem to
not care about making breaking API changes).
-Nate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140606/d92038ee/attachment.html>