NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Re-testing? (Score:1)
Just stray thought;
Would it be sensible to have some kind of "re-testing" infrastructure? E.g. when testing some new module before upgrade, one also checks if there are any other packages that would like re-testing, but with the upgraded version.
I'm thinking this "re-testing" would at least give authors a faster feedback, presumably reducing the necessity for downgrading in the long run. :)
Re: (Score:2)
Retesting would likely involve installing tests alongside the code, something we've never done before. It's been discussed, but no action taken.
Regrettably, when we have a bug crop up in our code, it's often difficult to find it without checking out an old branch and our CPAN dependencies are in a different checkout. I believe that svn externals would alleviate some of this pain, to be honest, but I'd still like to see "authority" become a first class concept on the CPAN (sort of the same way I'd like to
Re:Re-testing? (Score:1)
Retesting would likely involve installing tests alongside the code, something we've never done before.
It does?
Wouldn't it be enough just to register the wish for retesting when some modules are installed, and then give a proper warning such a module is (about to be) installed? (Later, the warning could be picked up by the build tool and perhaps acted upon.)
Reply to This
Parent