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

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 would *also* like the ability to pick a different bug tracking system to display information on search.cpan, but rt.cpan.org is intolerably slow. Faster would be much, much better -- and possibly a second grant for other improvements.
    --
    rjbs
    • FWIW, I've been in the process of moving my queues for {Test::,}WWW::Mechanize over to Google Code because of the slow. Also, because I like Google Code's bug tracking facilities more than RT.
      --

      --
      xoa

      • by rjbs (4671) on 2007.10.31 11:52 (#58699) Homepage Journal
        Yeah, I saw your recent post to module-authors (?). I don't mind RT per se, but rt.cpan.org's slowness, plus some other issues*, make it a big pain.

        * Some examples
        1. can't easily get a listing of all bugs for all my queues
        2. can't shut off wildly-spammy email interface
        3. logins are way, way too short-lived (compounds slowness)
        4. public/private URL for bug makes redirection after login hateful


        I'd love to see these fixed. I once offered to sponsor having them fixed, but the answer I got was something like, "No one should have to pay for this, we'd like to make it better for free."

        We're clearly getting *much* more than we're paying for, so I'm not grouchy about that. I'd just love to be able to pay for improvements, too.

        In the meantime, yeah, being bound to RT by default is problematic.
        --
        rjbs