Merge pull request #1559 from sdboyer/v040-release-prep

v0.4.0 release prep
tree: 45ef6ada0db2686ec56fa6e8b07772020ac6e0e7
  1. .github/
  2. cmd/
  3. docs/
  4. gps/
  5. hack/
  6. internal/
  7. testdata/
  8. vendor/
  9. website/
  10. .codeclimate.yml
  11. .gitattributes
  12. .gitignore
  13. .travis.yml
  14. analyzer.go
  15. analyzer_notwindows_test.go
  16. analyzer_test.go
  17. analyzer_windows_test.go
  18. appveyor.yml
  19. AUTHORS
  20. CHANGELOG.md
  21. CODE_OF_CONDUCT.md
  22. context.go
  23. context_test.go
  24. CONTRIBUTING.md
  25. CONTRIBUTORS
  26. doc.go
  27. Gopkg.lock
  28. Gopkg.toml
  29. LICENSE
  30. lock.go
  31. lock_test.go
  32. MAINTAINERS.md
  33. manifest.go
  34. manifest_test.go
  35. PATENTS
  36. project.go
  37. project_test.go
  38. README.md
  39. test_project_context_test.go
  40. txn_writer.go
  41. txn_writer_test.go
README.md

Dep

dep is a prototype dependency management tool for Go. It requires Go 1.8 or newer to compile. dep is safe for production use.

dep is the official experiment, but not yet the official tool. Check out the Roadmap for more on what this means!

For guides and reference materials about dep, see the documentation.

Installation

It is strongly recommended that you use a released version. Release binaries are available on the releases page.

On MacOS you can install or upgrade to the latest released version with Homebrew:

$ brew install dep
$ brew upgrade dep

If you're interested in hacking on dep, you can install via go get:

go get -u github.com/golang/dep/cmd/dep

Feedback

Feedback is greatly appreciated. At this stage, the maintainers are most interested in feedback centered on the user experience (UX) of the tool. Do you have workflows that the tool supports well, or doesn't support at all? Do any of the commands have surprising effects, output, or results? If not, please file an issue, describing what you did or wanted to do, what you expected to happen, and what actually happened.

Contributing

Contributions are greatly appreciated. The maintainers actively manage the issues list, and try to highlight issues suitable for newcomers. The project follows the typical GitHub pull request model. See CONTRIBUTING.md for more details. Before starting any work, please either comment on an existing issue, or file a new one.