Hello!
For a long time I'm using Test::Reporter. Now I participate in Vanilla
Perl project (http://win32.perl.org). I've started CPAN smoke.
I've come to several ideas regarding cpantesters. I want your opinion on
them.
1. YAML files on http://cpantesters.perl.org/ should include compiler
info. Most important example: distinguish between ActiveState Perl and
Vanilla Perl. I have both. Special case would be using gcc to compile
modules for ActiveState (don't know how to check for it).
Maybe also include some identifier (like Perl included in OS or compiled).
2. Develop http transport for Test::Reporter (partially done by me).
3. Modify CPANPLUS to report versions of dependencies even in case of
success. CPAN::Reporter already does this.
4. Modify CPAN::YACSmoke to have better configuration and to always skip
distributions in corresponding list in config.
5. We should have a list of hanging modules with comments for skipping
on CPAN smoking. Also list modules that require external libraries to
skip on Win32.
6. Add posibility to module developers (or anybody) to subscribe to FAIL
reports.
7. Dupe checks for reports.
8. External libraries versions also should be included in report.
9. AFAIK reports from people not on cpan-testers/AT/perl.org list are
manually checked. I don't want to subcribe to this list, if I want, I
read it via NNTP. With http transport there is no need for such checks.
10. CPAN::YACSmoke should also store dependecies in it's DB. If it is
testing module again it should report again it also if dependencies
versions changed.
There are some more ideas that are even not formed yet, but they depends
on realisation of these ideas.
P.S. Discussion of this may be done also on irc://irc.perl.org (#win32
or #perlqa). My nick is 'chorny'.
--
Alexandr Ciornii, http://chorny.net
