in reply to Re^3: CPAN module versioning for slight changes
in thread CPAN module versioning for slight changes

Did you hear about the Tester's issues?

All I'm saying is that one who knows better should either advise alternate avenues to do their testing before they send up a new version, or otherwise man up and Contribute to CPAN Testers.

  • Comment on Re^4: CPAN module versioning for slight changes

Replies are listed 'Best First'.
Re^5: CPAN module versioning for slight changes
by Anonymous Monk on Jan 05, 2016 at 02:13 UTC

    Um, what a weird thing to say, cpantesters is a volunteer organization

      One then shouldn't burden them knowingly and unnecessarily.

        One then shouldn't burden them knowingly and unnecessarily.

        You do realize you are calling uploading a distro to CPAN a burden

        To fix a mistake, you upload a new version

        That is only way to fix a mistake

        The volunteers will test this new version automatically

        There is no way to tell testers, you don't have to test this one, its was a stupid mistake of mine

        The volunteers do what they chose to do, some test everything hourly, some daily, some test dev versions only, some test once a week

        Its a burden they take on voluntarily

        They're not stupid either, they won't let tests run for half an hour

      Unless you were born yesterday, "volunteer" personal time is one thing, but in your house, would you volunteer your gas, electricity, time fixing equipment, time upgrading equipment for free for hundreds of thousands of requests per day?

      It costs money. Real money. If you still don't get it, let me cook 256k turkeys in your oven, every single day, for free, while you maintain it all, while you don't have any time to do a day job that pays.

Re^5: CPAN module versioning for slight changes
by jdv (Sexton) on Jan 06, 2016 at 17:12 UTC
    Did you hear about the Tester's issues?

    Not me - is there a resource shortage?

    All I'm saying is that one who knows better should either advise alternate avenues to do their testing before they send up a new version, or otherwise man up and Contribute to CPAN Testers.

    No doubt about it - I'd hope though that there is some leeway for new CPAN authors trying to figure things out. I'm not saying that CPAN should be a place to experiment, but sometimes its difficult to learn without actually trying. I try to test things out thoroughly on my box and on a Windows VM but I'm learning that there are seemingly a hundred different ways to trip up during the packaging. I'm trying to set up Travis CI as suggested on the github repo but that doesn't currently test on Windows (that I know of).

      "I'm trying to set up Travis CI as suggested on the github repo but that doesn't currently test on Windows"

      Unfortunately, it does not. That's why I have at least one VM set up with Strawberry on Windows to run it by before I put up to the CPAN. Although this is better than nothing, it still leaves you prone to having newer modules that are dependencies that you write yourself that are installed, so there is some risk of still having a failure or two when it hits the Testers.

      Doing what you can still helps though :)

      There's no doubt that it takes experience to learn, and new authors particularly have no choice but to get their feet wet (I did). From learning PAUSE, to naming modules, to uploading, to managing and keeping your namespaces clean and removing files that no longer need to be there... all the way to taking over another module of someone else who abandoned it.

      However, anyone experienced with either CPAN or managing a server infrastructure should be aware of the costs of doing so. Saying it's "volunteer" as an excuse is asinine.