summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorDavid Rodríguez <deivid.rodriguez@riseup.net>2019-04-08 16:45:35 +0200
committerDavid Rodríguez <deivid.rodriguez@riseup.net>2019-04-08 16:45:35 +0200
commit83e93785a0e9ecb553b90e383307c9bbeeba268e (patch)
tree77a2d97ab1c91d35ea8c175e80a56720de85ebcb /doc
parentc0c898b79db48c09158bcc9c335de66b55b5061c (diff)
downloadbundler-83e93785a0e9ecb553b90e383307c9bbeeba268e.tar.gz
Cleanup more stuff only needed for old rubies
Diffstat (limited to 'doc')
-rw-r--r--doc/contributing/BUG_TRIAGE.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/contributing/BUG_TRIAGE.md b/doc/contributing/BUG_TRIAGE.md
index 69aa3df0fd..fab584c7be 100644
--- a/doc/contributing/BUG_TRIAGE.md
+++ b/doc/contributing/BUG_TRIAGE.md
@@ -14,7 +14,7 @@ When you're looking at a ticket, here are the main questions to ask:
* Are the steps to reproduce the bug clearly documented in the ticket?
* Which versions of Bundler (1.1.x, 1.2.x, git, etc.) manifest this bug?
* 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?
+ * Which rubies (MRI, JRuby, Rubinius, etc.) and which versions (2.5, 2.6, 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.