travis: update go versions

[dvrkps]

No description provided.

[tleen]

Thanks for the contrib @dvrkps! The extra files included in the commit are a side-effect we are seeing from having the master and nextercism branches. They should not be in this commit, so see how we figure it out in #862.

Also while the nextercism travis file is outdated, the master one is actually ahead of this commit:

go:
  - 1.8.3
  - 1.9
  - tip

I wonder if we should be merging/rebasing nextercism against master periodically? @robphoenix thoughts?

[ferhatelmas]

@tleen you didn't ask me but I'd say definitely.

[ferhatelmas]

Changes look good to me but it's better to base PR into master, IMHO.

[ferhatelmas]

👍

[ferhatelmas]

I believe comment can be removed. 2.x isn't close.

[tleen]

@tleen you didn't ask me but I'd say definitely.

😳 Apologies @ferhatelmas ! I didn't want to spam people with mentions, I'll hit the whole group next time.

[dvrkps]

Can I add this in master branch also ?

[robphoenix]

I've changed this to be merged into the master branch.

This is good to merge with the suggested line deletion from @ferhatelmas

Thanks @dvrkps! I didn't know you could do this with Travis, learnt something 👍

[robphoenix]

I wonder if we should be merging/rebasing nextercism against master periodically? @robphoenix thoughts?

Yeah, for sure.

I've just rebased off master and pushed up to nextercism.

[robphoenix]

I've just rebased off master and pushed up to nextercism.

I haven't. I thought I had, but I had just pushed to my own repo origin rather than this one upstream.

If one of us rebases nextercism on master...

git fetch upstream master
git rebase upstream/master

...then they would have to force push up to this repo. This can have any number of negative consequences, including attaching that person to many of the commits

Honestly, I'm not sure of the best way to keep the nextercism branch in sync with master.

I'm going to merge this in to master, as the only change requested is not to do with something introduced in this PR and can be dealt with separately. And any conversation concerning branch maintenance can go in a separate issue, rather than spamming this PR.

Thanks again @dvrkps! 🎉