I think it's important to note here that this is not merely a case of a 48 hour silence, but one of at least one legit bug being ignored for 7 months
One of the two open "bugs" was a licensing issue, the other was a non-issue because that one had already been addressed in a previous release.
In any case, all bugs in the RT queue have now been addressed; the licensing "bug" is still open, metaperl's ticket and the duplicate report were rejected, as was an open feature request.
RT is there, but I prefer bug reports by e-mail. My CPAN mail address redirects to /dev/null because it accumulated an enormous amount of spam that after forwarding is pretty hard to filter accurately. As a result, I don't get e-mail notifications from new RT tickets. I never asked for an RT queue; it is created automatically and there is nothing CPAN authors can do about it.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||