On Wed, Aug 25, 2010 at 9:42 PM, Ben Tilly <bti...@gmail.com> wrote: > See > http://www.cpantesters.org/cpan/report/ad9d0e30-b03f-11df-9f7c-b27181b802a8 > > 5.13.4 is experimental. My hasn't been touched this year and succeeds > on perl 5.6 through 5.12 inclusive. Therefore failures on 5.13.4 are > more likely to be a bug in that development release of Perl than a bug > in the module. So the module doesn't need fixing, and I don't need to > hear about any problems.
That's not always the case. As perl internals change or features are deprecated in development releases of Perl, modules that rely on undocumented features (or the presence or absence of warnings) may break. Sub::Name is a great example of this. It relied on undocumented internals that broke in 5.13.3 due to a bug fix, which subsequently broke Moose and a lot of other things that depended on it. Having test reports was invaluable for detecting and diagnosing the issue (and in getting a patch sent upstream to the maintainer). I understand that you, personally, may not be interested in test results on development Perls, and you can choose whether or not to receive notifications of reports by email at https://prefs.cpantesters.org/ I believe the default is not to notify for development releases of perl, so if that isn't the case, please let us know so Barbie can investigate. Thank you. David
