Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
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.


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":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (5)
As of 2024-03-29 13:58 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found