Support vgo/go.mod & Tag New Release

[elithrar]

To support upcoming versioning support in the Go toolchain (beta in 1.11, prod in 1.12) -

• Add a go.mod file to this repo
• Tag a new release (likely v1.2.1 after I review the changes)
• Update Build Status in README to use Travis

[elithrar]

Will tag the new release after I fix the tests to run in CI via #47

[springeye]

+1

[carnott-snap]

Can we get an update on this; I dislike depending on pseudo versions for so long.

[eccles]

+1

[carnott-snap]

While I get that +1 messages are not productive, and I prefer emoji voting, it has been more than two years and there has been no progress. Should we consider forking and deprecating this repo?

[ptman]

@carnott-snap excellent solution. A fork could always be merged in the future if sensible

[carnott-snap]

I would hate to fragment the community, but if this repo is unmaintained, we may be better off rehoming it. Does anybody have a line into the maintainers?