comment on

All of our local patches are required to have the URL of the bug report attached to it. This allows future developers to come along and easily see the history, including whether or not the situation was resolved and if we can delete our local patch.

The end result of this has been several ignored bug reports, including one in which two module authors seem to feel that since their modules don't play well together, the fault likes with the other author. Regrettably, sometimes a fork is required :(

Cheers,
Ovid

The official Perl 6 wiki.

In reply to Re^2: Customizing cpan modules by Ovid
in thread Customizing cpan modules by jrsimmon

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.


Your skill will accomplish what the force of many cannot
	PerlMonks