diff options
| author | Patricia Arbona <arbonap@gmail.com> | 2017-08-03 20:04:16 -0700 |
|---|---|---|
| committer | Patricia Arbona <arbonap@gmail.com> | 2017-08-03 20:04:16 -0700 |
| commit | f4f128681c1a64ba6070304bd67e4d7b75d7ec44 (patch) | |
| tree | 89cde1e32278333cb0ffe18c431a99dcb7bc415e /doc | |
| parent | 9b1915acbce9d1796fff44f754adacff4f1e2f0b (diff) | |
| download | bundler-f4f128681c1a64ba6070304bd67e4d7b75d7ec44.tar.gz | |
Add Bug Triage Strategies
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/TROUBLESHOOTING.md | 3 | ||||
| -rw-r--r-- | doc/contributing/BUG_TRIAGE.md | 6 |
2 files changed, 9 insertions, 0 deletions
diff --git a/doc/TROUBLESHOOTING.md b/doc/TROUBLESHOOTING.md index d310d85d40..6b1f831c70 100644 --- a/doc/TROUBLESHOOTING.md +++ b/doc/TROUBLESHOOTING.md @@ -41,6 +41,9 @@ list](http://bundler.io/compatibility.html), and make sure that the version of B If these instructions don't work, or you can't find any appropriate instructions, you can try these troubleshooting steps: + # Update to the latest version of bundler + `gem install bundler` + # Remove user-specific gems and git repos rm -rf ~/.bundle/ ~/.gem/bundler/ ~/.gems/cache/bundler/ diff --git a/doc/contributing/BUG_TRIAGE.md b/doc/contributing/BUG_TRIAGE.md index 3c34db048b..b70c1285fe 100644 --- a/doc/contributing/BUG_TRIAGE.md +++ b/doc/contributing/BUG_TRIAGE.md @@ -16,6 +16,12 @@ When you're looking at a ticket, here are the main questions to ask: * Which operating systems (OS X, Windows, Ubuntu, CentOS, etc.) manifest this bug? * Which rubies (MRI, JRuby, Rubinius, etc.) and which versions (1.8.7, 1.9.3, etc.) have this bug? +Strategies for triaging a ticket: + * Be sure to ask the user to output the entirety of their `bundle env`. Sometimes users forget to post all of their `bundle env` output in the issue. + * After seeing the output of the user's `bundle env`, try to replicate the user's problem in your current environment. Only portions of the code base is changed in each release, so there's a good chance your version of bundler might have the same bug. + * If you're having trouble replicating their issue with your current environment, slowly try to incorporate the user's environment setup. As in, this is where you begin matching their environment. For example, try switching to the user's version of Ruby, RubyGems, RVM, et cetera, step by step. + * Is the user running the latest version of bundler? If not, ask them to update by running `gem install bundler`. There's a chance that the newest version of bundler has already solved their problem. + If you can't reproduce the issue, chances are good that the bug has been fixed already (hurrah!). That's a good time to post to the ticket explaining what you did and how it worked. If you can reproduce an issue, you're well on your way to fixing it. :) |