Shlomi, a bit of rant here and then some constructive suggestions.
On Sun, Jul 10, 2011 at 2:21 PM, Shlomi Fish <shlo...@shlomifish.org> wrote: > On Sun, 03 Jul 2011 13:39:55 -0700 > Serguei Trouchelle <s...@cpan.org> wrote: > >> >> In real world, they are very REALISTIC. People don't update modules in >> production just because they can. Only when they must. >> > > Well, the question is how old is old. If you test a very old version which > isn't in production anywhere then you just sending me junk reports. None of us can really know that. We only have a close estimate that the majority of test reports are coming from automated smoke testers. Those real world companies unfortunately hardly send in any test report. They just try to install the module. Swear that it does not work and conclude that perl is unreliable. Ideally they would send in the test report at that point and we would know. As much as I'd like that, that's not the case. I understand that you don't have the time to research which version of your dependencies are required but do you expect the CPAN testers to research this? Or do you expect them to *always* use the latest and never test even with a version that was release last months? 3 months ago? A year ago? Where should the tester set this limit? You can chose several strategies: 1) Leave as it is now and get the failure reports 2) Set it to the highest number currently on CPAN and make some people angry that you force upgrade their software 3) Look at the testers, see what is the biggest number that is still failing and set it to += 0.01 and upload. If you still get the errors then repeat 3 for the next release. 4) There might be other strategies. Anyone? I hope this can help you. regards Gabor
