Maybe also include a link to the web site of the CPAN Testers:
Lhttp://www.cpantesters.org/
and to the wiki
Lhttp://wiki.cpantesters.org/
Gabor
On Wed, Sep 10, 2008 at 1:25 PM, Martin Evans [EMAIL PROTECTED] wrote:
Hi CPAN testers,
I am about to make new release of one of the modules I
Given the purpose, I would suggest just including a link to the wiki.
It has information on how to get set up to send tests and they can get
to the reports page from there. Having a choice of two websites
decreases the chance they'll look at either. (Economists have
determined that choice is
# from David Golden
# on Wednesday 10 September 2008 04:07:
I would suggest just including a link to the wiki.
It has information on how to get set up to send tests and they can get
to the reports page from there. Having a choice of two websites
decreases the chance they'll look at either.
On Wed, Sep 10, 2008 at 09:52:16PM +0200, nadim khemir wrote:
If Perl is to be enterprise worthy someday, it has to allow companies to smoke
their own modules using the same mechanism as standard perl modules but beind
a privacy curtain. My belief is that the whole toolchain shouls be
* nadim khemir [EMAIL PROTECTED] [2008-09-10 21:55]:
I'm tired of seing reports for failure on windows when the
module is not a windows module at all.
Ideally you should be using Devel::CheckOS, of course, in which
case your failures would turn into NAs.
Regards,
--
Aristotle Pagaltzis //
nadim khemir wrote:
If Perl is to be enterprise worthy someday, it has to allow companies to smoke
their own modules using the same mechanism as standard perl modules but beind
a privacy curtain. My belief is that the whole toolchain shouls be
installable in a private setup. PAUSE, CPAN,
