Some observations, from my limited number of patches/bug reports on CPAN:

1. modules that are heavily used tend to have fairly good turn-around on bug reports & patches (which may just be because heavily used modules have more patches and bug reports). Case in point: DBD::mysql still has some outstanding unicode bugs, but AFAICT that's mostly because nobody can figure out a good way to solve them, and there is at least some discussion on the RT about them. (Note that DBD::mysql also gets a lot of "bogus" bug reports due to its not very robust test suite). The patches I submitted were incorporated in the next release (which took about a month and a half IIRC).

2. Some modules really only have a few users, and the author might have moved on. Authors of those modules (myself included) may not be very actively maintaining them. I try to keep Audio::LADSPA more or less up to date with bugs, but it can take a week or two before I can work up the energy to check out a patch or bug report on it. My schedule is pretty hectic at the moment and I can't really afford to spend a lot of time working on stuff that isn't directly related to my job during the day.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re: Losing faith in CPAN - unresponsive module authors by Joost
in thread Losing faith in CPAN - unresponsive module authors by andreas1234567

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.