[Catalyst] 5.55 and forcing auth

[Torsten Seemann]

Chisel Wright wrote:
> On Tue, Nov 15, 2005 at 07:10:50PM +0100, Sebastian Riedel wrote:
> 
>>How much Cat tests have you written? 
> 
> I haven't reported any bugs. Nor have I had any reported to me.
> 
> To be fair, the onus should be on the reporter to produce a failing test
> case for a bug, but I strongly suspect that most of us wouldn't know
> where to start.

It's important to remember there are a range reporter skill levels! eg.

  1. "this doesn't work"
  2. "here's a simple code snippet which used to work but now fails"
  3. "this module is broken in the latest version, here's a patch!"

These reflect the different skills of Catalyst users. One wouldn't 
expect reporter 1 to be able to write a test case, or even reporter 2.

In cases 1 and 2, if a Catalyst author is the one who FIXES the bug, 
they are in the BEST position to write the test.

In fact they are probably doing themselves a dis-service overall if they 
don't write a test; especially given the number of things which have 
broken in the 5.4/5.5 Catalyst series.

But I agree that in most cases, Reporter 3 probably should be able to 
write a test case along with their patch. (even though the module author 
could probably do it more efficiently and accurately).

Have you considered using a bugzilla or bug ticketing system?

The reason I ask is that I've emailed to authors and posted to 
catalyst-devel (in the past) and catalyst-dev (recently) actual patches 
against trunk (including for .pod), but they often get ignored.

--Torsten Seemann