Re: Move dev release tarballs to GitHub?

--000000000000ac9d2b05dbf5815c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Apologies for going silent since I sent my initial email, I've been trying
to learn a new keyboard and it's not been great for productivity.

ribs- Thank you for considering it and starting some research.

Deleting them from the main CPAN and letting them remain on backpan seems
like a very reasonable direction.  The needs of CPAN and backpan are very
different.  Backpan is significantly larger, but gets significantly less
traffic and has lower performance requirements.  For example, there's no
requirement to support fast mirroring.

As Ask pointed out, the data shows that these files get very little
traffic.  Elsewhere in the thread it was noted that the same content can be
retrieved from Git.  Not many people will be inconvenienced.

Todd said:

> I=E2=80=99m unclear who decides if it=E2=80=99s OK for me to delete the d=
ev versions of
> Perl I=E2=80=99ve done. I=E2=80=99m happy to do it. Maybe we should put a=
 policy or
> suggestion into the release manager=E2=80=99s guide as a first step?


I think that's what we're trying to figure out.  Unless someone (rjbs?)
comes up with a reason why not to, it would be cool  to have a policy that
dev releases get deleted TBD months after the next release, or something
similar.

Thanks-

-R


On Tue, Apr 5, 2022 at 2:54 AM Ask Bj=C3=B8rn Hansen <[email protected]> wrote:

> That=E2=80=99d make sense to me, deleting the old images and letting them=
 just be
> on backpan. That should allow whatever tooling depends on recent releases
> being in the regular CPAN mirrors to still work.
>
> Looking at 3 days of www.cpan.org logs only the most recent development
> image seems to have been downloaded more than the background noise of
> everything getting a request now and then because web crawlers. (And the
> most recent development image by just number of downloads recently is les=
s
> popular than about a dozen very old not-development releases).
>
> I put a CSV of the counts of =E2=80=9Cperl5-=E2=80=9C URLs temporarily at
> https://tmp.askask.com/os/cpan/cpan-perl-downloads-2022-04-05-02_13_21.cs=
v
>
>
> Ask
>

--000000000000ac9d2b05dbf5815c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Apologies for going silent since I sent my initial=C2=A0em=
ail, I&#39;ve been trying to learn a new keyboard and it&#39;s not been gre=
at for productivity.<div><br></div><div>ribs- Thank you for considering it =
and starting some research.</div><div><br></div><div>Deleting them from the=
 main CPAN and letting them remain on backpan=C2=A0seems like a very reason=
able direction.=C2=A0 The needs of CPAN and backpan are very different.=C2=
=A0 Backpan is significantly larger, but gets significantly less traffic an=
d has lower performance requirements.=C2=A0 For example, there&#39;s no req=
uirement to support fast=C2=A0mirroring.</div><div><br></div><div>As Ask po=
inted out, the data shows that these files get very little traffic.=C2=A0 E=
lsewhere in the thread it was noted that the same content can be retrieved =
from Git.=C2=A0 Not many people will be inconvenienced.</div><div><br></div=
><div>Todd said:</div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I=
=E2=80=99m unclear who decides if it=E2=80=99s OK for me to delete the dev =
versions of Perl I=E2=80=99ve done. I=E2=80=99m happy to do it. Maybe we sh=
ould put a policy or suggestion into the release manager=E2=80=99s guide as=
 a first step?</blockquote><div><br></div><div>I think that&#39;s what we&#=
39;re trying to figure out.=C2=A0 Unless someone (rjbs?) comes up with a re=
ason why not to, it would be cool=C2=A0=C2=A0to have a policy that dev rele=
ases get deleted TBD months after the next release, or something similar.</=
div><div><br></div><div>Thanks-</div><div><br></div><div>-R</div><div><br><=
/div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Tue, Apr 5, 2022 at 2:54 AM Ask Bj=C3=B8rn Hansen &lt;<a href=3D"ma=
ilto:[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div style=3D"overflow-wrap: break-word;">=
That=E2=80=99d make sense to me, deleting the old images and letting them j=
ust be on backpan. That should allow whatever tooling depends on recent rel=
eases being in the regular CPAN mirrors to still work.<div><br></div><div>L=
ooking at 3 days of <a href=3D"http://www.cpan.org" target=3D"_blank">www.c=
pan.org</a>=C2=A0logs only the most recent development image seems to have =
been downloaded more than the background noise of everything getting a requ=
est now and then because web crawlers. (And the most recent development ima=
ge by just number of downloads recently is less popular than about a dozen =
very old not-development releases).</div><div><br></div><div>I put a CSV of=
 the counts of =E2=80=9Cperl5-=E2=80=9C URLs temporarily at=C2=A0<a href=3D=
"https://tmp.askask.com/os/cpan/cpan-perl-downloads-2022-04-05-02_13_21.csv=
" target=3D"_blank">https://tmp.askask.com/os/cpan/cpan-perl-downloads-2022=
-04-05-02_13_21.csv</a></div><div><br></div><div><br></div><div>Ask</div></=
div></blockquote></div>

--000000000000ac9d2b05dbf5815c--