Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Wednesday July 25, 2007
04:05 AM

RT, RT, RT, not Email, damn it!

[ #33880 ]

No offense, but if you send me an email with a bug report, there's a good chance that I won't get to it right away and if I don't get to it right away, there's a good chance I won't get to it ever.

On the other hand, if you post that bug report to the appropriate CPAN RT queue (and my modules generally even list a nice email address for you to do so without using the Web site, if you don't want to), then I will get to the bug report. Eventually. I forget email. I lose email. I don't lose RT.

I know many other CPAN authors with this same complaint. Please don't send us email about bugs. Use RT.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I have the following mutt keybinding to bounce mail to RT myself. They're never going to learn to use the right address, so I'm not trying to teach.

    macro pager \~ "brtmailadresshere@example.com\n\ns=bouncedtort\n\n" "Bounce to RT"
    macro index \~ "brtmailadresshere@example.com\n\ns=bouncedtort\n\n" "Bounce to RT"

    This bounces the message to RT, and saves a copy of the original message in a folder called "bouncedtort". Since I get RT messages by mail too, this effectively *replaces* the message by one that h

  • As a module author, I only wish RT felt more streamlined to use. Some annoyances:
    • Different URLS for the public and logged in versions of tickets.
    • Clicking the link to login, only to have RT tell me "You have been logged out". Huh? That implies I was logged in already, and am now just doing busy work to login again.
    • There's no "Really Resolve" button. First I have to use the resolve link and complete an additional step to submit the "update" form.
    • Yeah, RT has its nits, but as a central place for me to be able to keep bug reports and requests, it's what we've got.

      And on a completely unrelated note, I've added the V|version switch to TAP::Parser's runtests, as you requested :)

    • Clicking the link to login, only to have RT tell me "You have been logged out". Huh? That implies I was logged in already, and am now just doing busy work to login again.

      Gawd, I thought it was just me. I seem to get tripped up with the Bitcard process a lot.

  • RT has a horrible interface, both for reporting bugs and for authors. I would far rather people report bugs in my code to me by email. So much so that if they do report them via RT, I have written a script that will pull them out and email them to me. With emailed bug reports, they sit on my laptop and are available to me even when I'm off the net. Bug reports in RT are utterly useless when I am, for instance, visiting the family over christmas, which is my most productive time for bugfixing.

    The corre

    • Right. This was the author saying what he wanted everybody to use.

      I presume he already had said so in the module documentation and is ticked off that people didn't follow it. Of course, if he didn't, then he really doesn't have a leg to stand on with this rant. :)

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
      • Yes, I do have that listed in my modules. However, drhyde is right that individuals should report bugs the way the author wants them reported. I shouldn't have suggested that everyone do it my way, even if my way is right ;)