Skip to content

Conversation

ttaylorr
Copy link
Contributor

This pull request upgrades our testing infrastructure to use Go 1.8.

  • Travis: bumped in the .travis.yml to use 1.8.
  • AppVeyor: Go 1.8 isn't in on cinst yet, so let's install it ourselves.
  • CircleCI: upgrade through go 1.8 Homebrew/homebrew-core#10048

/cc @git-lfs/core

@ttaylorr ttaylorr merged commit c367e94 into master Feb 17, 2017
@ttaylorr ttaylorr deleted the go1.8 branch February 17, 2017 00:06
@sschuberth
Copy link
Member

Does it really make sense to jump at new Go versions immediately after their release? Waiting for the next minor release (like 1.8.1) would have the benefit of getting additional fixes for bugs that were rushed out with the release, and we'd have a higher chance of the release being available as a Chocolatey package.

@technoweenie
Copy link
Contributor

I think testing with the new version is good. Though we probably could've held off on updating the appveyor build until it's available on chocolatey.

We're not releasing LFS 2.0 for at least a week, so we still have time to evaluate go 1.8.

@ttaylorr ttaylorr mentioned this pull request Mar 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants