To help people who upload modules to CPAN lots of people test them. I have been doing this for while following instructions on the CPAN Testers Wiki. However the automation instructions are very specific to dave's set up. So I wrote my own scripts.

cpantest.sh is my script which fires off cpan for the releases I'm testing. autocpantest automates the testing of recent modules. Its not all automated, I still have to approve the sending of failure reports. The script is quite frankly quite bad and would probably be better as some perl. Perhaps when I've taught myself some I might rewrite it.

With all this in place I should start shooting up the leaderboard

The first perl 5.10.1 release candidate was released the other day. As mst says if you don't test it now and it breaks for you when its released its your fault. As a good cpan tester I've added it to my testing setup.

Since I care about OpenGuides for the Randomness Guide to London I made sure to submit a test report for it.

While I was doing this I also added perl 5.8.9 to my setup. I also changed my setup slightly by pre-installing Moose and Catalyst since thats what all the cool perl programmers are using these days. Since installing and testing their dependency chains was burning a lot of cpu, time and bandwidth every time a new module based on them was updated or added to CPAN