This repo is becoming the standard way to build and test go repositories outside of travis

[alcortesm]

The README from this project starts with this sentence:

This project contains the common CI configuration for all source{d} Go projects...

And this is true. But we have been moving other functionality recently from other projects to this one, for instance, now that we use glide in some projects, a makefile is needed, and we have been adding targets here for building and testing outside of travis.

It looks as if we were broadening the focus of this project to a more general approach to building and testing go projects.

Is this so? Is there a firm commitment to this trend?, Can we explain that in the readme and also document the expected ways a developer should interact with this new functionality?

[smola]

So far we are not recommending users to use make to build (go get should be used instead) or to resolve vendor directory (we now checkin the vendor directory). Some projects with more strange dependencies (e.g. C) still provide make-based commands documented for end users.

There is no change in sight at the moment.