Best way to report issues (and patches) with rtir

RTIR
1

Hello,

now that it seems like RTIR mailing list traffic is picking up again, I
was wondering if people knew the best way of reporting bugs and/or
sending patches?

I’ve been mucking around with rtir1.1.5, mostly because 1.0.5 needs
rt3.0 which has a whole heap of annoying issues, and have come up with
quite a few things, but am unsure how to report them and get them fixed
as quickly as possible (i.e, use rt3.fsck, mailing list, mail to jesse
…?)

As an example, I’ve updated
http://rt3.fsck.com/Ticket/Display.html?id=6403, including a patch for
some of the issues, but never got a response.
Mostly I’m concerned that people are duplicating each other’s work, and
that patches may be ignored.

So, if anyone knows a good method of contributing to RTIR, I’d (and
perhaps others) would appreciate knowing about it.

Thanks

signature.asc (189 Bytes)

2

Hello,

now that it seems like RTIR mailing list traffic is picking up again, I
was wondering if people knew the best way of reporting bugs and/or
sending patches?

So, I think that the right thing is likely: submit tickets to
rt3.fsck.com (in the RTIR queue) and mention to this list that they’re
there. We’re working on a setup that will gateway from RT to the list
and vice versa. RTIR 1.1 hasn’t gotten as much attention internally as
we’d like, though that looks like it’s set to change fairly soon. As a
small company, we really do have to focus our efforts where we can find
paying customers and traditionally very few organizations using RTIR
have been able to help underwrite development, either by paying for
features or by purchasing support contracts. Over the past few months,
we’ve been working hard on the business side of something that should
help this out significantly, but the ink isn’t on the paper yet, so I
can’t say much about it.

For our part, we’ll try to be better about getting RTIR patches rolled
into the svn repository faster.

Best,
Jesse