Shmuel Fomberg <shmuelfomb...@gmail.com> writes: > On Tue, Nov 13, 2012 at 7:42 AM, Andreas Koenig wrote: > > Shmuel Fomberg writes: > > >> Why would you inform all the dependent modules if the root cause is > >> already known? From a single RT ticket which needs to be pushed you > want > >> to multiply that onto all affected modules? > > > > because I'm trying to simulate an automated process, as Andreas Koenig > > suggested. > > Rereading my own mail I cannot recognizee that I suggested that. > > > Quoting: > Fill the bugtrackers and keep track of the tickets yourself, so we can > learn from the experience. > > I may misunderstood your meaning, but sound to me like a good idea anyway...
OK, I notice you have started and openened a couple of tickets 81189 Depending on Test::Class open Webservice-InterMine 81190 Depending on Test::Class new Net-ZooKeeper-Lock 81191 Depending on Test::Class open ParseUtil-Domain 81192 Depending on Test::Class new App-PM-Website 81193 Depending on Test::Class resolved Template-Plugin-Bootstrap-Pagination 81194 Depending on Test::Class new CHI 81195 Depending on Test::Class new WebService-Cmis 81196 Depending on Test::Class new Net-Thumper 81197 Depending on Test::Class new CHI-Driver-TokyoTyrant And I find the same boilerplate text on all: Hi. I notice that you module is depending on Test::Class. Test:Class have a high test failure rate, and this means that a lot of the people that want to install you module won't be able to. Worse, you can't even see this failures in your CPAN testers reports, as dependency fail is not reported. Can you please fix that? Thanks, Shmuel. >From my experience this text lacks a few more facts about what the current state of the issue is. I think such a ticket should point to the ticket in the bugtracker of Test::Class that reports the bug. It should mention which release of Test::Class is affected and a link and/or text that illustrates what "high failure rate" means in the concrete case. All these informations help to track the whole story and improve the chance that the tickets are useful for others. In the concrete case * I find several open tickets at rt.cpan.org and cannot recognize which you are talking about. * I find out there are four pull requests at https://github.com/adrianh/test-class/pulls and cannot identify if any of them has to do with your complaint. It would be interesting to know whether one of those fixes the issue you are seeing. * I find the matrix is mostly green: http://matrix.cpantesters.org/?dist=Test-Class%200.37 I wonder whether "high failure rate" is the appropriate term. The following last point I have is more a matter of taste: I would wish that the sentence "Can you please fix that?" be dropped. Then the ticket probably gets more of a chance to be taken as a help for others. But feel free to ignore this last one, it's by far not so important as the others. Thanks, -- andreas
