Re: Move dev release tarballs to GitHub?
[email protected] ("Ricardo Signes") Sun, 03 Apr 2022 13:52:23 -0400
| Newsgroups | perl.cpan.workers |
|---|---|
| Message-ID | <[email protected]> |
--8df654c1399d4a318e20a3a535df22b4
Content-Type: text/plain
On Fri, Mar 25, 2022, at 19:30, Robert Spier wrote:
> Would you consider, instead of pushing them to CPAN, posting them to GitHub using the releases functionality?
Robert,
I have considered it, and I think the short answer is, "It's worth considering." It will break some amount of downstream tooling, like CPAN::Perl::Releases and, downstream of that, `plenv install`. That makes me sort of reluctant to jump in with both feet. It doesn't seem like a terrible idea or anything, just not something I feel like is an obvious win.
On the other hand, quite possibly pruning old dev releases aggressively and allowing them to be plucked from backpan is probably quite simple, and I suspect we can do this to older releases without requiring ever releaser to take individual action. Would this be much of a help?
To test how well the tools will work when the release is only on backpan, I have boldly deleted 5.11.4 via PAUSE. I'll check back on this in a week.
--
rjbs
--8df654c1399d4a318e20a3a535df22b4
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Fri, Mar 25,=
2022, at 19:30, Robert Spier wrote:<br></div><blockquote type=3D"cite" =
id=3D"qt" style=3D""><div dir=3D"ltr"><div>Would you consider, instead o=
f pushing them to CPAN, posting them to GitHub using the releases functi=
onality?<br></div></div></blockquote><div><br></div><div>Robert,<br></di=
v><div><br></div><div>I have considered it, and I think the short answer=
is, "It's worth considering." It will break some amount of downst=
ream tooling, like CPAN::Perl::Releases and, downstream of that, <code s=
tyle=3D"border-top-width:1px;border-right-width:1px;border-bottom-width:=
1px;border-left-width:1px;border-top-style:solid;border-right-style:soli=
d;border-bottom-style:solid;border-left-style:solid;border-top-color:rgb=
(204, 204, 204);border-right-color:rgb(204, 204, 204);border-bottom-colo=
r:rgb(204, 204, 204);border-left-color:rgb(204, 204, 204);border-image-s=
ource:initial;border-image-slice:initial;border-image-width:initial;bord=
er-image-outset:initial;border-image-repeat:initial;border-top-left-radi=
us:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border=
-bottom-left-radius:3px;background-image:initial;background-position-x:i=
nitial;background-position-y:initial;background-size:initial;background-=
repeat-x:initial;background-repeat-y:initial;background-attachment:initi=
al;background-origin:initial;background-clip:initial;background-color:rg=
b(246, 246, 246);font-family:menlo, consolas, monospace;font-size:90%;pa=
dding-top:1px;padding-right:3px;padding-bottom:1px;padding-left:3px;">pl=
env install</code>. That makes me sort of reluctant to jump in wit=
h both feet. It doesn't seem like a terrible idea or anything, jus=
t not something I feel like is an obvious win.<br></div><div><br></div><=
div>On the other hand, quite possibly pruning old dev releases aggressiv=
ely and allowing them to be plucked from backpan is probably quite simpl=
e, and I suspect we can do this to older releases without requiring ever=
releaser to take individual action. Would this be much of a help?=
<br></div><div><br></div><div>To test how well the tools will work when =
the release is only on backpan, I have boldly deleted 5.11.4 via PAUSE.&=
nbsp; I'll check back on this in a week.<br></div><div><br></div><div>--=
<br></div><div>rjbs</div></body></html>
--8df654c1399d4a318e20a3a535df22b4--