🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
00:31 librasteve_ left 06:25 finanalyst joined 06:39 finanalyst left, finanalyst joined 08:39 finanalyst left
[Coke] Any thoughts on switching to a bi-monthly or quarterly release cycle by default in 2026? 11:54
lizmat I guess it depends on the release manager(s) ? 11:57
and the number of changes ?
[Coke] Sure, we can always make a decision each month, just wondering if we're at a point in number of commits per month in 2025 that indicates we should reduce the default # per year. 12:00
(and we could still do a release on an off month if needed, etc.) 12:01
No rush, no pressure, just curious if anyone has any thoughts.
pros: reduce efforts for release, cons: might be negative marketing. 12:02
Geth ¦ Blin: coke self-assigned Create ARM template to setup environment for Blin testing github.com/Raku/Blin/issues/45 13:40
¦ Blin: coke self-assigned Blin runs should be resumable github.com/Raku/Blin/issues/40 13:43
jdv you mean run blin on arm? iirc arm is slow cause there is no jit. 13:44
14:13 vrurg left 14:14 vrurg joined 14:26 vrurg left 14:31 vrurg joined 15:32 finanalyst joined
[Coke] ... no 15:43
I mean automatically create an azure VM capable of running blin.
(mainly so I don't have to rely on keeping this hand-rolled one alive) 15:44
added a link to the arm docs to clarify, thanks 15:45
18:25 finanalyst left
jdv oh. so azure gets to take "arm" now? I didn't know! 22:51
once we get it communityified or whatever it should be easier to blin. that's what i was blocking on when i was trying to do something with it. 22:52
i think i'm still using my hand patched one from...(and docker says) "19 months ago". yup, its old. 22:53
in any case sounds cool for you 22:54