On Saturday 30 September 2006 01:16, Alexandr Ciornii wrote:
> 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).

That would be a good idea.

> 2. Develop http transport for Test::Reporter (partially done by me).

Good idea. In addition to submitting the test report by email.

> 3. Modify CPANPLUS to report versions of dependencies even in case of
> success. CPAN::Reporter already does this.

Good idea.

> 4. Modify CPAN::YACSmoke to have better configuration and to always skip
> distributions in corresponding list in config.

Right.

> 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.

Sounds good.

> 6. Add posibility to module developers (or anybody) to subscribe to FAIL
> reports.

Right. Via email or RSS. It was discussed previously, how authors get 
notifications of RT issues, but don't get notificiation of the module smoke 
tests.

> 7. Dupe checks for reports.

That would be good.

> 8. External libraries versions also should be included in report.

That may require some support from EU::MM/M::B/etc. because one cannot know in 
advance which external libraries are used by the modules.

> 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.

What do you mean?

> 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.

Sounds good.

Regards,

        Shlomi Fish

---------------------------------------------------------------------
Shlomi Fish      [EMAIL PROTECTED]
Homepage:        http://www.shlomifish.org/

Chuck Norris wrote a complete Perl 6 implementation in a day but then
destroyed all evidence with his bare hands, so no one will know his secrets.

Reply via email to