develooper Front page | perl.perl5.porters | Postings from December 2020

Re: committers: do you use dromedary?

Thread Previous | Thread Next
Steve Hay via perl5-porters
December 26, 2020 00:17
Re: committers: do you use dromedary?
Message ID:
On Thu, 24 Dec 2020, 20:32 Ricardo Signes, <>

> Once upon a time, a sponsor provided a server called dromedary.  It was a
> big beefy hunky of hardware with a lot of RAM and a bunch of cores.  It
> compiled perl very fast.  Some people used it for bisecting, some for
> testing a bunch of different versions of perl, and so on.
> Later, a second dromedary existed and was used, but less.
> I've been trying to get a handle on the various resources we rely on, and
> dromedary has come up.  If there's to be a third iteration of this box:  *Who
> will use it and for what?*
> I guess I'd start off thinking it's like the old one:  used by committers
> as a powerful place to do a lot of compiling and testing.  But is that
> right?  If you are a committer and would (or would not!) use it, please say
> so, and let me know what you'd be using it for.  (What else we might use a
> bunch of compute for is another question.  This is more about a box where
> you'd have a shell.)

I only used it as a staging post for uploading Perl releases from, as used
to be recommended in the RMG until recently. What do people do now? Upload
directly from their own machines? That's probably okay most of the time,
but having an official Perl box to put RCs of security releases on was also
useful when sending links to vendors for testing -- we have no replacement
for that right now and sending out links to random Dropbox shares isn't so

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About