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.
-
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.
|