The Rubinius issue tracker is http://github.com/rubinius/rubinius/issues.
To be useful, tickets must be concise, focused, and actionable. If not, the ticket will languish and become clutter. Accordingly, tickets must fall into one (or more) of the following categories:
If your issue doesn't fit into one of the categories, it is not invalid. It is simply not appropriate for a ticket.
Give your ticket a specific, preferably short title.
Give your ticket appropriate tags.
Give enough detail about the issue.
uname -ais usually good (if there are any "unknown" fields in it, please elaborate on those.)
Unless for some reason impossible, please use a pull request to create the patchset. It is the easiest way for us to review and apply the changes. If opening a pull request is impossible, please use git-format-patch and add a link to it using gist.github.com, pastie.org or a similar service.
Suppose the following spec exists and is failing:
describe "Kernel.format" do it "is accessible as a module function" do Kernel.format("%s", "hello").should == "hello" end end
"[PATCH] No method 'format' on Kernel (Module)"
"patch core spec"
The method 'format' is not available as a module function of Kernel.
$ bin/mspec spec/ruby/core/kernel/format_spec.rb Started .E 1) Kernel.format is accessible as a module function ERROR No method 'format' on Kernel (Module):
The method 'format' already exists but has not been set as a module function. This pull request does so.
After the pull request is applied:
$ bin/mspec spec/ruby/core/kernel/format_spec.rb Started .. Finished in 0.016031 seconds 2 examples, 2 expectations, 0 failures, 0 errors