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 ]

janus (3624)

janus
  (email not shown publicly)
http://janus.errornet.de/

Journal of janus (3624)

Tuesday October 02, 2007
03:14 AM

use CPAN; no GOOGLE;

[ #34588 ]

Today i just found the most annoying ticket on rt.cpan.org after i filed a new bug yesterday:
http://rt.cpan.org/Public/Bug/Display.html?id=26344

If i take this bug as what it is - a bug - can someone fix and close it please?
It's even a critical one and i'm all for closing it as soon as possible!

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 feel it's kind of annoying when you are used to report bugs in CPAN modules via rt.cpan.org. But the author is entitled to choose the tools he prefers, so he's right about letting people know that he prefers bug reports via a channel he's more comfortable with.

    A good compromise would be if it was possible to redirect automatically the bug queue of Test::Reporter [cpan.org] into the author's favourite bug tracker, as well as redirecting the e-mails to bug-Test-Reporter@rt.cpan.org. But it probably won't happen: rt.

    • I would have even filed the bug at google if no extra registration would be required - an automatism would be very nice indeed.
      • The extra registration is so that we don't get all the noise from spammers. Look at the Test::Harness some time for an example.
        --

        --
        xoa

  • How is it annoying? Sounds like the author can ask for whatever he wants if you want to use his software. No rules that people who release on CPAN must use a given tracker.
    --

    --
    xoa

    • My only rule is that i want to file bugs without prior registration.
      And in the meantime the authors replied already and they are keeping track of RT, too... so my fear was actually for nothing.
      But my rule/claim still remains the same.
  • The META.yml spec is picking up keys for authors to refer to resources, like version control, bug reporting etc.

    I imagine that once the toolchain has had a chance to catch up, you'll be able to add a key of some sort to your Makefile.PL and then Test::Reporter and search.cpan.org etc will know where to send people.