I think this is a great approach. It's interesting to note that they're pushing the same thing with Pugs, and it seems to be working very nicely. The catch phrase bantered around is usually something along the lines of, "I'll trade you a bug fix for a test."
Not only does it give a way to verify the bug fix, but it forces a bit more effort on the part of the reporter. It's not enough effort to be prohibitive (in my experience, anyway), yet it's just enough to raise the quality of the bug reports. All around, it seems like a really nice idea.
-
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.
|