On Wed, Sep 03, 2008 at 10:39:07PM -0400, David Golden wrote: > If you mean don't test 1.01 when 1.02 has a PASS, then I agree. My > approach with CPAN::Reporter::Smoker is to test only the latest > release -- even if "latest" was 5+ years ago. I think we should > discourage testing older distributions entirely.
Should, or shouldn't? There's a lot of value for users (and some for authors) in knowing that some old module still works in 5.10.0. There's more value for authors in knowing that it *fails* in 5.10.0, at least if they still care about the module. And we can't know whether they care about it - just because it's 5 years old doesn't mean they don't care, it just means that no-one's found any bugs in it. eg, my NestedMap module. If that didn't work in 5.10, I'd want to know. > Note that this is potentially something that we could "enforce" by > checking if a distribution is no longer the most current and > discarding reports that refer to older releases. But see my idea about a "CP5.8AN". Authors shouldn't be notified, I agree, but discarding reports entirely doesn't seem like a good idea. -- David Cantrell | A machine for turning tea into grumpiness What is the difference between hearing aliens through the fillings in your teeth and hearing Jesus in your heart?
