Hi Karen

Obviously I suggested as one mechanism to reduce the size of the disk space used.

As for versions, perhaps zap 5.10.0 and older?

And yes, I'm aware there may be older versions running in the wild, but the point is to manage the CPAN (Tester) infrastructure within the capabilities of the volunteers, not to support everything endlessly.

On 06/07/17 14:10, Karen Etheridge wrote:
I'm not sure why you'd suggest it then? What Perl versions would *you*
suggest be removed from cpantesters?

I would contend that all results are valuable. Helping preserve
backwards compatibility is one of the great things that the cpantesters
network brings us.

On Wed, Jul 5, 2017 at 8:15 PM, Ron Savage <r...@savage.net.au
<mailto:r...@savage.net.au>> wrote:

    Hi Karen

    I paused over that statement, but I'm sure there are persons with
    the Perl 5 porters group, for example, who may be able to specify
    same, in a way I'm not qualified to do :-).

    On 06/07/17 11:50, Karen Etheridge wrote:

        Define "versions of Perl which are no longer supported"?

        On Wed, Jul 5, 2017 at 6:40 PM, Ron Savage <r...@savage.net.au
        <mailto:r...@savage.net.au>
        <mailto:r...@savage.net.au <mailto:r...@savage.net.au>>> wrote:

            Hi Doug

            How much change would result, and how difficult would it be,
        if you
            deleted data pertaining to version of Perl which are no longer
            supported?


            On 06/07/17 10:03, Doug Bell wrote:

                I've gotten a few requests to remove data from CPAN
        Testers. I don't
                know if that has ever been done, and I'm not sure if I'd
        like to
                start
                doing it, but there are some situations that I do not
        think can
                be fixed
                any other way:

                Chad Granum (Exodist) wants to see the latest releases of
                Test-Simple
                first, but their version numbers are lower than some
                previously-released
                versions (and we cannot, to my knowledge, be the arbiter of
                those kind
                of problems). This results in issues
                like http://matrix.cpantesters.org/?dist=Test-Simple
        <http://matrix.cpantesters.org/?dist=Test-Simple>
                <http://matrix.cpantesters.org/?dist=Test-Simple
        <http://matrix.cpantesters.org/?dist=Test-Simple>> and
                http://beta.cpantesters.org/chart.html?dist=Test-Simple
        <http://beta.cpantesters.org/chart.html?dist=Test-Simple>
                <http://beta.cpantesters.org/chart.html?dist=Test-Simple
        <http://beta.cpantesters.org/chart.html?dist=Test-Simple>> where
                these invalid versions are shown first.

                There's also simply a _lot_ of data on CPAN Testers, some of
                which is
                for distributions that are no longer installable on CPAN
                (distributions
                available only on Backpan). This slows down a lot of
        otherwise
                simple
                procedures. If there was a way to move this data to another
                place, a lot
                of the normal operation of the site would be faster.
        However,
                partitioning the site like this would likely require a
        bunch of
                changes
                to downstream systems (which would have to decide which
        side of the
                partition they want). This doesn't sound like an
        insurmountable
                problem:
                The APIs default to "all" and you can opt-in to the faster
                "cpan" partition.

                We could just fix the Test-Simple issue (and other similar
                issues) by
                deleting the data that will never be relevant again:
        Test-Simple
                2.0 was
                never released and only got development versions. Then
        we could
                discuss/develop longer-term solutions for the other issues.

                Does anyone have any other thoughts/opinions?

                Doug Bell
                d...@preaction.me <mailto:d...@preaction.me>
        <mailto:d...@preaction.me <mailto:d...@preaction.me>>
                <mailto:d...@preaction.me <mailto:d...@preaction.me>
        <mailto:d...@preaction.me <mailto:d...@preaction.me>>>




            --
            Ron Savage - savage.net.au <http://savage.net.au>
        <http://savage.net.au>



    --
    Ron Savage - savage.net.au <http://savage.net.au>



--
Ron Savage - savage.net.au

Reply via email to