On Thu, Sep 4, 2008 at 4:19 AM, Eric Wilhelm <[EMAIL PROTECTED]> wrote: >>Some of these proposal would be easier in CPAN Testers 2.0, which will >>provide reports as structured data instead of email text, but if "exit >>0" is a straw that is breaking the Perl camel's back now, then we >>can't ignore 1.0 to work on 2.0 as I'm not sure anyone will care >>anymore by the time it's done. > > What are the issues in that time? Code or non-code?
mostly $job, @family, %life stuff > Yes. Further, if you can detect new tools from old, you have enough > information to filter the results. > > Hah! You know, you have their e-mail address, right? You can just send > them nagging mail about how their tools are FAIL! ;-) I'd already come to the same realization, actually. > So, what do you show the author and/or users by default? That is > possibly still rather sticky, but making it adjustable (perhaps > according to the maintainer by default) should allow reasonable people > to be happy enough. That's the stuff that I'd probably defer to CPAN Testers 2.0. Once test reports are structured data, it will be much easier to filter on toolchain, environement, etc. Right now, someone would have to effectively "screen scrape" the reports -- with variations for CPANPLUS, CPAN::Reporter and their different formats over time. It could be done -- this is Perl after all -- but that's not where I'm interested in putting my energies. -- David
