On Mon, Nov 12, 2012 at 4:26 PM, Steffen Schwigon wrote: > Shmuel Fomberg writes: > > On Mon, Nov 12, 2012 at 1:27 AM, Steffen Schwigon wrote: > >> 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. There are people that are trying to fix CPAN manually, > > most notably (at least recently) is Shlomi Fish. You can see his > > emails asking for comaint popping up in the authors list. I'm lazier > > then him, and seek systematic solution to systematic problem. > > Ok, I generally understand your rationale, so even if I'm not convinced, > let's continue: how would you proceed after you have opened tickets on > all dependent modules?
I'm still thinking about what to write in the ticket itself, btw. I think that a general ticket will be the best - "you are depending on a dep that have a high failure rate, and so your module will probably won't install on many of your clients. can you please stop using it?" I don't say what I already know - on which systems it fails, that there is ticket open with a patch. as I said - simulating a automated machine. then I will track what happens. probable replies: 1. STFU. I don't care 2. I looked on the problem and it does not affect my module on my target platforms. so, I don't care 3. Pinging Test::Class author, and getting him to fix it 4. Pinging T::C author, got a comaint and fixed it myself 5. ticket ignored I want to show that by bugging the module authors that depend on a module, maybe one of them will be motivated enough to fix it. And I'm going only for the directly depending modules, as they are the most likely to care, to be able to do something about it, and keeping the 'noise' to minimum. Shmuel.
