I should elaborate on this slightly. I think it is valid to have a bug
in the tracker for failing specs under these circumstances:
1. If work has started on the bug and it requires a place for discussion.
2. If there's already a bug filed with *useful* discussion.
3. If there's a patch that requires review. This mostly falls under (1) above.
If you want to help tidy up JRuby's bug tracker, feel free to close as
"incomplete" any RubySpec bugs that are solely there to be bugs (i.e.
no useful discussion, no patches, etc). There may be a lot of them.
Any objections to this policy?
- Charlie
On Thu, Nov 17, 2011 at 3:01 AM, Charles Oliver Nutter
<head...@headius.com> wrote:
> I think it's no longer in our interest to clog the bug tracker with
> failing specs. They're failing and we have tags for them, so we know
> about them. Only user bugs should go in the tracker, since they
> represent a failure that affected a user.
>
> This is a new policy so don't feel bad if you filed RubySpec failures
> as bugs recently :) I have been by far the worst offender.
>
> - Charlie
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
