in reply to Re^3: When is it time to stop posting to CPAN?
in thread When is it time to stop posting to CPAN?

"I do like the nice things the ecosystem gives me, e.g. RT and CPAN Testers"

Github has 'issues' for rt, and allows the use of continued integration testing (free tiers exist for most OS IIRC) for cpan testers.

  • Comment on Re^4: When is it time to stop posting to CPAN?

Replies are listed 'Best First'.
Re^5: When is it time to stop posting to CPAN?
by tobyink (Canon) on Oct 14, 2020 at 09:48 UTC

    I much prefer RT over GitHub issues. I have all (or pretty much all) of my CPAN releases on Github, but have disabled the Github issue trackers in favour of RT.

    CI like Travis and AppVeyor are great and I use them for many of my distributions, but there have been many times that my code has passed all its tests on Travis, but CPAN Testers have found issues. CPAN Testers will be testing your distribution in a wider variety of environments. While CIs might get you a handful of operating systems and a bunch of different Perl versions, CPAN Testers will give you a variety of CPU architectures and OS versions, different C compilers, older versions of your dependencies, different combinations of your optional dependencies, different locales and environment variables, etc. Yes, you can test some of this with CI if you think through and anticipate the combinations in advance, but CPAN Testers gives you a set of random variations that is very valuable.

    toby döt ink
[reply]

      I agree with everything you have said here. However, none of it is a reason to publish something on CPAN which would otherwise not belong there.

      🦛

[reply]
      Another nice feature of CPAN Testers is Slaven Rezic :-)
[reply]

In Section Meditations