On Sun, Nov 18, 2012 at 6:15 PM, Andreas Koenig wrote: > > OK, I notice you have started and openened a couple of tickets >
Here is my spreadsheet where I track my tickets: https://docs.google.com/spreadsheet/ccc?key=0Asx6ks0ZzUccdHM3bktQcEY5Y1d6NzVJX1VpM1hVUGc And I find the same boilerplate text on all: > 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. > It was done by purpose. I want to see how many authors will investigate, and what they will do. So I don't add any actual info on why these failures happened. One author even asked "what do you want me to do?", and I replied that I'm just providing a warning. what does he want to do? > * 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. > It will just fail on non-*unix platform. mostly green indeed. > 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. > A call for action is important. English is not my native language, and if someone has better wording for it I'll use it. Shmuel.
