This feed does not validate.
<updated>2025-06-22T17:38:43</updated>
^
line 12, column 32: (15 occurrences) [help]
<published>2025-06-22T17:38:43</published>
^
line 13, column 30: (15 occurrences) [help]
<updated>2025-06-22T17:38:43</updated>
^
In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation.
line 26, column 0: (26 occurrences) [help]
<img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e6 ...
<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>The Perl Foundation</title><link rel="alternate" type="text/html" href="http://news.perlfoundation.org/"/><link rel="self" type="application/atom+xml" href="http://news.perlfoundation.org/atom.xml"/><id>tag:news.perlfoundation.org,2010-03-22://18</id><updated>2025-06-22T17:38:43</updated><generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 6.2.2</generator><entry> <title>Maintaining Perl (Tony Cook) April 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_tonyc_april_2025"/> <id>tag:news.perlfoundation.org,2025-06-22:/post/maintaining_perl_tonyc_april_2025</id> <published>2025-06-22T17:38:43</published> <updated>2025-06-22T17:38:43</updated> <summary> <![CDATA[ Tony writes: 2025/04/01 Tuesday 0.22 #23151 check CI results, fix minitest and re-push 1.77 #23160 try to decode how the NEED_ stuff works, try leont’s suggestion and test, push for CI 0.82 #22125 check smoke results, rebase and push 0.50 #21878 consider how to implement this 0.53 ppc #70 testing, comment 3.84 2025/04/02 Wednesday 0.23 #23075 rebase and squash some, push for ]]> </summary> <author> <name>alh</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Tony writes:```[Hours] [Activity]2025/04/01 Tuesday 0.22 #23151 check CI results, fix minitest and re-push 1.77 #23160 try to decode how the NEED_ stuff works, try leont’s suggestion and test, push for CI 0.82 #22125 check smoke results, rebase and push 0.50 #21878 consider how to implement this</p> <h1> 0.53 ppc #70 testing, comment</h1> <p>3.84</p> <p>2025/04/02 Wednesday 0.23 #23075 rebase and squash some, push for CI 0.98 test-dist-modules threaded testing: check CI results, remove 5.8, clean up commits, push for CI 0.10 #23075 check CI results and apply to blead</p> <h1> 0.28 test-dist-modules: check CI, open PR 23167</h1> <p>1.59</p> <p>2025/04/03 Thursday 0.37 #23151 check CI results, open PR 23171 1.60 #17601 side-issue: check history, testing, find an unrelated problem, work on a fix, testing 0.20 #17601 side-issue: push fix for CI, comment and mark</p> <h1> #17601 closable</h1> <p>2.17</p> <p>2025/04/07 Monday 0.15 #22120 follow-up 1.57 #23151 add suggested change, testing and push 0.62 #23172 review and comment 0.20 #23177 review, research and apply to blead 0.37 #17601 side-issue: check CI results, add perldelta, cleanup commit message, open PR 23178 0.60 #23022 clean up, add perldelta, push for CI</p> <h1> 0.73 #22125 re-check, rebase, push for CI</h1> <p>4.24</p> <p>2025/04/08 Tuesday 0.53 #17601 research, minor fix and comment 0.08 #22125 fix test failure 0.48 #17601 side-issue: testing, research and comment 0.55 #16608 reproduce, code review</p> <h1> 1.62 #16608 try to work out a reasonable solution</h1> <p>3.26</p> <p>2025/04/09 Wednesday 1.23 #17601 side issue: add a panic message, research and comment 2.40 #16608 research, try to reproduce some other cases, comment, work on fixes, tests, work class initfields similar bug 1.83 #16608 fix an issue with smartmatch fix, work on initfields fix, testing, perldelta, push for CI, smoke-me 0.33 #17601 test another build configuration, minor fix and push 0.28 #23151 testing</p> <h1> 0.23 #17601 comment</h1> <p>6.30</p> <p>2025/04/10 Thursday 0.32 #16608 fix a minor issue and re-push 0.13 #23165 review updates and approve 2.28 look into smoke test failures, ASAN detected leak from op/signatures, debugging, make #23187 2.28 op/signatures leak: debugging, work it out (I think), work</p> <h1> on a fix, testing, push for CI/smoke-me</h1> <p>5.01</p> <p>2025/06/14 Saturday 3.45 #23022 re-check, minor re-work, testing, push</p> <h1> 0.35 #23187 op/signatures leak: comment, some re-work</h1> <p>3.80</p> <p>2025/04/15 Tuesday 1.15 #23187 consider re-work, minor fix, testing, perldelta, push for CI 0.70 document that TARG isn’t pristine and the implications, open #23196 0.60 #16608 check smoke results, debugging and fix, push for CI/smoke 1.13 #22125 clean up commit history, testing, perldelta, more</p> <h1> testing and push for CI/smoke</h1> <p>3.58</p> <p>2025/04/16 Wednesday 0.23 #23196 edits as suggested and push 1.50 #23187 check CI results, investigate ASAN results, which appear unrelated, open PR 23203 0.67 #23201 review, research a lot, approve 0.20 #16608 check CI results, make PR 23204 0.63 #1674 review history and research, comment since I’m</p> <h1> confused</h1> <p>3.23</p> <p>2025/04/22 Tuesday 0.17 #23207 review, research and approve 0.92 #23208 review, testing and comment 1.80 #23202 review, testing 0.67 #23202 more review, testing 0.37 #23202 more review, comments 0.25 #23208 research and comment</p> <h1> 0.43 #23215 research</h1> <p>4.61</p> <p>2025/04/23 Wednesday 0.30 #23202 review responses 0.80 #23172 review updates, approve 0.22 #1674 research 1.63 #1674 more research, minor change, testing, push for CI 0.45 #3965 testing 0.23 #3965 more testing, comment and mark “Closable?” 0.10 #1674 review CI results and make PR 23219</p> <h1> 1.22 #4106 debugging, research and comment</h1> <p>4.95</p> <p>2025/04/24 Thursday 0.22 #23216 review and approve 0.08 #23217 review and approve 0.08 #23220 review and approve 1.10 #23215 testing, look if we can eliminate the conditional from cSVOPx_sv() on threads (we can’t directly, the non- pad sv is used at compile-time), approve 0.35 #23208 review, research, comments 1.27 #4106 research 2.70 #4106 testing for potential bugs and misbehaviour, chainsaw for w32_fdpid and make it like everyone else,</p> <h1> testing and push for CI</h1> <p>5.80</p> <p>2025/04/28 Monday 0.35 #20841 comment 2.38 #22374 minor fixes, testing, force push to update, comments 0.13 #23226 review and approve 0.70 #23227 review, research, check build logs and comment</p> <h1> 0.45 #23228 review, testing and comments</h1> <p>4.01</p> <p>2025/04/29 Tuesday 0.42 #23228 check updates and approve 0.63 #23227 testing and comment 1.07 #23225 start review</p> <h1> 1.23 #23225 more review</h1> <p>3.35</p> <p>2025/04/30 Wednesday 1.28 #23227 review, testing, research and approve with comment 0.68 #4106 check results, look for existing tests that might test this, testing 2.23 #4106 review history, work on a new test, testing, push for CI 0.83 #23232 review docs, open Dual-Life/experimental#22 which</p> <h1> adjusts the version range and links to the docs</h1> <p>5.02</p> <p>Which I calculate is 64.76 hours.</p> <p>Approximately 33 tickets were reviewed or worked on, and 2 patcheswere applied.```</p> ]]> </content></entry><entry> <title>PEVANS Core Perl 5: Grant Report for May 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/pevans_core_dev_may_2025"/> <id>tag:news.perlfoundation.org,2025-06-17:/post/pevans_core_dev_may_2025</id> <published>2025-06-17T16:07:53</published> <updated>2025-06-17T16:07:53</updated> <summary> <![CDATA[ Paul writes: As earlier reported, I managed to make some progress on the `faster-signatures` work, as well as some other things. 2 Bugfix for assigning operator https://github.com/Perl/perl5/pull/23242 1 Exception handling during defer/finally https://github.com/Perl/perl5/pull/23244 4 faster-signatures and CVf_NOSNAIL performance work https://github.com/leonerd/perl5/tree/faster-signatures 2 Signature helper functions in class.c https://github.com/Perl/perl5/commit/3e684b47ee6bec19678c13d8f10b6824ab4c286b Total: 9 hours ]]> </summary> <author> <name>alh</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Paul writes:</p> <p>As earlier reported, I managed to make some progress on the<code>faster-signatures</code> work, as well as some other things.</p> <ul><li>2 = Bugfix for assigning <code>^^=</code> operator<ul><li>https://github.com/Perl/perl5/pull/23242</li></ul></li><li>1 = Exception handling during defer/finally<ul><li>https://github.com/Perl/perl5/pull/23244</li></ul></li><li>4 = faster-signatures and CVf_NOSNAIL performance work<ul><li>https://github.com/leonerd/perl5/tree/faster-signatures</li></ul></li><li>2 = Signature helper functions in class.c<ul><li>https://github.com/Perl/perl5/commit/3e684b47ee6bec19678c13d8f10b6824ab4c286b</li></ul></li></ul> <p>Total: 9 hours</p> ]]> </content></entry><entry> <title>Maintaining Perl 5 Core (Dave Mitchell): May 2025</title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_dave_mitchell_may_2025"/> <id>tag:news.perlfoundation.org,2025-06-17:/post/maintaining_perl_dave_mitchell_may_2025</id> <published>2025-06-17T15:57:50</published> <updated>2025-06-17T15:57:50</updated> <summary> <![CDATA[ Dave writes: A bit of a quiet month. I checked blead for any performance regressions compared with 5.40.0, using Porting/bench.pl. I found only one significant one: UTF8 string literals were inadvertently no longer being created Copy-on-Write. I created a PR which improves how OPs are dumped on threaded builds. This will make certain types of debugging easier in the future. Fixed a bug. Tweaked my ParseXS AST ]]> </summary> <author> <name>alh</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Dave writes:</p> <p>A bit of a quiet month.</p> <ul><li><p>I checked blead for any performance regressions compared with 5.40.0,using Porting/bench.pl. I found only one significant one: UTF8 stringliterals were inadvertently no longer being created Copy-on-Write.</p></li><li><p>I created a PR which improves how OPs are dumped on threaded builds.This will make certain types of debugging easier in the future.</p></li><li><p>Fixed a bug.</p></li><li><p>Tweaked my ParseXS AST PR.</p></li></ul> <p>Summary:</p> <ul><li>0:30 GH #23308 - MY_CXT doesn't like a 1-byte struct</li><li>11:09 improve CONST/GV OP dumping</li><li>2:50 investigate performance regressions</li><li>0:48 process p5p mailbox</li><li>0:32 reduce smoke failures</li><li>5:58 refactor Extutils::ParseXS</li></ul> <p>Total:</p> <ul><li>21:47 TOTAL (HH::MM)</li></ul> ]]> </content></entry><entry> <title>Maintaining Perl (Tony Cook) March 2025</title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_tonyc_march_2025"/> <id>tag:news.perlfoundation.org,2025-05-09:/post/maintaining_perl_tonyc_march_2025</id> <published>2025-05-09T07:21:56</published> <updated>2025-05-09T07:21:56</updated> <summary> <![CDATA[ Tony writes: 2025/03/03 Monday 0.83 #23015 research and comment 0.22 #23012 research and comment 0.45 #22827 review updates and re-approve 0.68 amagic_call/coverity follow-up, work on a fix, commit message wording, check is clangsa picks this up 0.15 amagic_call/coverity, commit message, push for CI 0.28 #22642 review updates and approve 0.78 #23044 research and comment 3.39 2025/03/04 Tuesday 0.80 #23012 comment, ]]> </summary> <author> <name>alh</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Tony writes:</p> <p>```[Hours] [Activity]2025/03/03 Monday 0.83 #23015 research and comment 0.22 #23012 research and comment 0.45 #22827 review updates and re-approve 0.68 amagic_call/coverity follow-up, work on a fix, commit message wording, check is clangsa picks this up 0.15 amagic_call/coverity, commit message, push for CI 0.28 #22642 review updates and approve</p> <h1> 0.78 #23044 research and comment</h1> <p>3.39</p> <p>2025/03/04 Tuesday 0.80 #23012 comment, consideration, comment some more 1.38 #23043 review, research 0.63 #23043 more review, comment 0.30 #23056 review and comment 0.08 #23058 review and approve 0.17 #23061 review and approve 0.10 #23062 review and approve</p> <h1> 0.25 #23041 review</h1> <p>3.71</p> <p>2025/03/05 Wednesday 0.27 #23053 review discussion and comment 0.12 #23056 review update and approve 0.12 #23057 review and comment 0.10 #23059 review and comment 0.17 #23063 review and comment 1.20 #22423 clean up, push for CI, message to p5p 0.28 coverity amagic_call PL_op:check CI results and open PR 23071 0.57 #23054 testing, comment 0.35 #23070 review and approve 0.38 #23072 review and approve 0.20 #23069 review and approve</p> <h1> 0.27 #22423 write a perldelta and push, make PR 23073</h1> <p>4.03</p> <p>2025/03/06 Thursday 0.18 #23063 review updates and approve 0.15 #23059 review updates and approve 1.10 #23075 review, research and comments 0.73 #23076 testing, debugging test failure, comment 0.75 #23076 more debugging, research and comment 0.23 #23077 review and approve 0.10 #23078 review and approve</p> <h1> 1.22 #16608 research</h1> <p>4.46</p> <p>2025/03/10 Monday 0.47 github notifications 0.23 #23079 review updates and approve 0.73 #23075 review discussion and comment 0.27 #23080 review and comment 0.47 #23095 research and comment 0.25 #23082 review and approve 0.22 #23083 review and comment 0.18 #23094 review change and links, comment 0.35 #23083 review changes, comment</p> <h1> 0.93 unicode discussion #p5p and testing</h1> <p>4.10</p> <p>2025/03/11 Tuesday 0.15 review overnight #p5p discussion 0.08 #23097 review change and discussion, approve 0.18 #23071 apply to blead (manually, github UI wigged out complaining I was trying to do a squash merge) 0.10 #23073 apply to blead manually, github is confused here too 0.30 review coverity results</p> <h1> 1.52 #23037 review discussion, research and comment</h1> <p>2.33</p> <p>2025/03/12 Wednesday 0.37 #23075 follow-up 1.30 #23076 look into hooks branch and comment 0.53 #23012 review latest and approve 0.17 #23087 review and approve 0.52 #23088 review, notice a separate typo and make PR 23099, approve 0.35 #23092 review, think, approve</p> <h1> 0.32 #23093 review, check C::J::XS and approve</h1> <p>3.56</p> <p>2025/03/13 Thursday 0.37 #23091 review and approve 1.98 #23096 review... 0.65 #23096 review and approve</p> <h1> 0.47 #23037 #p5p discussion</h1> <p>3.47</p> <p>2025/03/17 Monday 1.25 #23075 read discussion, research and comment 0.30 #23108 review and approve, comment 0.83 #23120 start review, research 0.52 #23120 comment</p> <h1> 0.57 #23114 research and comment</h1> <p>3.47</p> <p>2025/03/18 Tuesday 0.30 review leonerd’s av_store API improvements discussion 1.60 #23075 research, review overnight discussion (side trip into a coverity scan report) 1.32 #23075 more review, work on adding sv_vstring_get to</p> <h1> D::PPP, testing, push for CI</h1> <p>3.22</p> <p>2025/03/19 Wednesday 0.22 #23108 review discussion, verify overload reordering, comment 1.02 #23112 review and approve 0.62 #23121 review, comment and approve 0.80 look into why dist-modules tests aren’t testing threaded perls, testing</p> <h1> 0.68 more dist-modules, try to work what introduced 5.8 failure</h1> <p>3.34</p> <p>2025/03/20 Thursday 0.33 github notifications 0.08 #23120 comment 1.37 #23144 review, review history 0.10 #23144 approve 0.38 #23074 see if downstream fixed it (hard to be sure at this point) 0.87 #21877 rebase and push, add comments and mark ready for</p> <h1> review</h1> <p>3.13</p> <p>2025/03/24 Monday 0.77 #23152 research and comment 2.18 #23151 review code, work on a reproducer, comment, test a fix (needs tests), try to work out where/how to test</p> <h1> 0.98 #23151 try to work up a testable case</h1> <p>3.93</p> <p>2025/03/25 Tuesday 1.68 #23151 more work on a testable case 0.97 #23081 research, code profiling and approve with comment</p> <h1> 0.85 #23108 testing and comment</h1> <p>3.50</p> <p>2025/03/26 Wednesday 0.33 ppc#70 comment 0.80 av_store thread, review discussion, consider some replies 0.35 #23150 comment 0.60 #23153 review and comment 0.32 #23153 follow-up, comment 0.22 #23157 review and approve</p> <h1> 0.58 #23156 review and comments</h1> <p>3.20</p> <p>2025/03/27 Thursday 2.35 #23075 check ppport.h CI results, rewrite since the API changed, testing and push for CI again</p> <h1> 1.13 #23075 test cleanup, testing</h1> <p>3.48</p> <p>2025/03/31 Monday 0.43 #23163 review and approve 0.95 #23162 review and comment 0.23 #23161 review and approve 0.27 #23153 review and approve 1.07 #23075 cleanup, trying to understand the code 1.62 #23151 work up a test code, testing, perldelta, push for</p> <h1> CI</h1> <p>4.57</p> <p>Which I calculate is 60.89 hours.</p> <p>Approximately 60 tickets were reviewed or worked on, and 2 patcheswere applied.```</p> ]]> </content></entry><entry> <title>Maintaining Perl (Tony Cook) February 2025</title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_tonyc_february_2025"/> <id>tag:news.perlfoundation.org,2025-05-09:/post/maintaining_perl_tonyc_february_2025</id> <published>2025-05-09T07:18:02</published> <updated>2025-05-09T07:18:02</updated> <summary> <![CDATA[ Tony writes: 2025/02/03 Monday 0.28 ppc 30/31 list catch up 0.13 github notifications 0.08 #22955 briefly comment 0.62 #22956 review, testing and comment 0.23 #22957 review and approve 0.30 #22958 review and approve 0.42 #22970 review and approve 0.92 #22917 review, research, testing and approve 2.98 2025/02/04 Tuesday 0.45 github notifications 0.23 #22955 review and approve 1.27 #22963 ]]> </summary> <author> <name>alh</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Tony writes:</p> <p>```[Hours] [Activity]2025/02/03 Monday 0.28 ppc 30/31 list catch up 0.13 github notifications 0.08 #22955 briefly comment 0.62 #22956 review, testing and comment 0.23 #22957 review and approve 0.30 #22958 review and approve 0.42 #22970 review and approve</p> <h1> 0.92 #22917 review, research, testing and approve</h1> <p>2.98</p> <p>2025/02/04 Tuesday 0.45 github notifications 0.23 #22955 review and approve 1.27 #22963 review and comments</p> <h1> 1.23 #22967 review, comments</h1> <p>3.18</p> <p>2025/02/05 Wednesday 2.02 #22959 debuggging, work up a fix and push for CI</p> <h1> 1.25 #22423 debugging, work on tests</h1> <p>3.27</p> <p>2025/02/06 Thursday 0.95 #22967 review updates and approve 0.85 #22959 review CI results and fix an issue 0.78 #22423 work on a fix 0.18 #22959 review CI results, perldelta, make PR 22976</p> <h1> 1.00 #22423 debugging tied hash case</h1> <p>3.76</p> <p>2025/02/10 Monday 0.12 #22976 re-check, apply to blead 0.17 #22963 review updates and approve 0.15 #22910 review updates and approve 0.82 #22940 review updates and comment 1.72 #22927 review, benchmarking, approve and comment</p> <h1> 1.80 #22423 try to work up a fix for tied hash cases</h1> <p>4.78</p> <p>2025/02/11 Tuesday 1.07 #22423 more tied hash (internet down), get it working, some cleanup, need to work on related ticket but need detail, on hold for now 1.03 #21877 work on issue with fix, reproduce and isolate 0.23 #21877 work out what’s going on (in /(?{ s!!x! })/ moves the PV of $_ as the match is going through the PV of $_),</p> <h1> which is a known RE problem.</h1> <p>2.33</p> <p>2025/02/12 Wednesday 0.23 #22940 review updates and approve 0.72 #22985 review and approve 0.35 #22986 review and comment 0.40 #22752 work on rebase</p> <h1> 2.38 #22752 more rebase</h1> <p>4.08</p> <p>2025/02/17 Monday 0.10 #22766 work out what happened here 0.68 #22884 testing, comment 1.05 #22971 review and comments 0.35 #22960 review, research and comment 1.12 #22989 review, research, comment 0.40 #23007 review and comment</p> <h1> 1.20 #22884 testing and comment</h1> <p>4.90</p> <p>2025/02/18 Tuesday 1.02 #22989 review update, debugging i386 CI, comment 0.87 #22423 debug CI failure 0.40 #22989 review discussion, research and comment</p> <h1> 0.48 #22423 fix CI error, push for CI</h1> <p>2.77</p> <p>2025/02/19 Wednesday 0.55 #22989 research and comment, look over changes and approve 1.72 #22423 debug test issues 1.07 #22423 fixes, push for more CI 0.80 #22880 comment some more</p> <h1> 0.63 perldelta for switch re-work, make PR 23013</h1> <p>4.77</p> <p>2025/02/20 Thursday 0.77 #23016 review test failure, review cpan code and comment 1.55 #23010 review discussion, research 1.05 #23010 research</p> <h1> 0.40 #23013 minor change and apply to blead</h1> <p>3.77</p> <p>2025/02/24 Monday 2.20 #23019 research and comments 0.77 #23022 work on reproduce and reproduce, comment</p> <h1> 2.27 #23022 debugging, work on a fix, push for CI</h1> <p>5.24</p> <p>2025/02/25 Tuesday 0.28 #23022 fix porting error and re-push 0.25 #23016 open tokuhirom/Perl-Lexer#14 0.17 #23020 comment 0.62 #23015 look into Prima, comment 0.48 #p5p win32 performance discussion 0.33 #23012 review 1.08 #23012 review and comments</p> <h1> 0.23 #23022 look into CI failure and fix</h1> <p>3.44</p> <p>2025/02/26 Wednesday 0.38 #23022 check CI results, cleanup and push 0.13 #23025 briefly comment 2.12 review coverity scan results 0.68 review clang sa results, fix one issue and push for CI</p> <h1> 0.80 #21877 approach from the other direction (sv_gets)</h1> <p>4.11</p> <p>2025/02/27 Thursday 0.17 clang sa fix: check CI results and make PR 23034 0.25 #23025 briefly comment (and look at dmq’s MSVC failure for wellrng) 0.43 #22971 review updates and approve 0.08 #23034 discussion catch up 0.25 #p5p discussion re RNGs 0.30 #23026 comment 0.08 #22971 look over perldelta and comment 0.08 #23029 review and approve 0.50 #22907 invoke the PSC</p> <h1> 0.52 clangsa: review more reports</h1> <p>2.66</p> <p>2025/02/28 Friday</p> <h1> 0.37 #23037 comment</h1> <p>0.37</p> <p>Which I calculate is 56.41 hours.</p> <p>Approximately 39 tickets were reviewed or worked on, and 2 patcheswere applied.```</p> ]]> </content></entry><entry> <title>Maintaining Perl 5 Core (Dave Mitchell): March - April 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_dave_mitchell_march_april_2025"/> <id>tag:news.perlfoundation.org,2025-05-09:/post/maintaining_perl_dave_mitchell_march_april_2025</id> <published>2025-05-09T07:12:40</published> <updated>2025-05-09T07:12:40</updated> <summary> <![CDATA[ Dave writes: This is my monthly report on work done during Mar and Apr 2025, covered by my TPF perl core maintenance grant. I spent most of my time continuing to refactor Extutils::ParseXS, as a precursor to adding reference-counted stack abilities to XS. In particular, I've recently pushed a large PR, intended to be merged once 5.42.0 is done, which converts ParseXS to create an AST for each XSUB it ]]> </summary> <author> <name>alh</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Dave writes:</p> <p>This is my monthly report on work done during Mar and Apr 2025, covered bymy TPF perl core maintenance grant.</p> <p>I spent most of my time continuing to refactor Extutils::ParseXS, as aprecursor to adding reference-counted stack (PERL_RC_STACK) abilities toXS.</p> <p>In particular, I've recently pushed a large PR, intended to be mergedonce 5.42.0 is done, which converts ParseXS to create an AST for each XSUBit parses. This has three main benefits.</p> <p>First, it separates out the parsing and code generation.</p> <p>Second, it splits up the parsing of XSUBs into manageable segments. Forexample, the longest sub that is concerned with parsing XSUBs is now 182lines long and the longest concerned with code generation is 342 lines.Prior to this PR, the longest (concerned with both parsing and codegeneration) was 1412 lines.</p> <p>Third, the parsing state is now stored in the AST's nodes, close to whereit's relevant, rather than all state being stored in one big confusingExtutils::ParseXS hash.</p> <p>In summary: in 5.40.0 and before, the XS parsing code was a buggy, mostlyuntested, unmaintainable mess, that nobody understood properly, and whichwas risky to modify. It is now modern and (hopefully) can accept changeseasily.</p> <p>Summary:</p> <ul><li>0:34 #23074 BBC breaks Crypt::SMIME</li><li>1:00 fix Test -deparse failures</li><li>13:40 process p5p mailbox</li><li>0:12 reduce smoke failures</li><li>111:26 refactor Extutils::ParseXS</li></ul> <p>Total:* 126:52 (HH::MM)</p> ]]> </content></entry><entry> <title>RakuAST Project Final Grant Report</title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/sseifert_rakuast_final"/> <id>tag:news.perlfoundation.org,2025-04-18:/post/sseifert_rakuast_final</id> <published>2025-04-18T10:45:04</published> <updated>2025-04-18T10:45:04</updated> <summary> <![CDATA[ Stefan has now come to a conclusion of his efforts with RakuAST. This mammoth task started previously by Jonathan Worthington. In the time since his award of the grant, he has made 823 commits to RakuAST, and his overall contribution to Raku in the past couple of years is second only to the very prolific Elizabeth Mattijsen. His contributions can be viewed on github. It is impossible to describe all ]]> </summary> <author> <name>Saif Ahmed</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Perl 6 Development" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Raku Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/055a79c25ab8cda5303fea032fa22e735d042328/Camelia RakuAST.svg" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Stefan ( <a href="https://github.com/niner">niner</a> ) has now come to a conclusion of his efforts with <a href="https://news.perlfoundation.org/post/sseifert-rakuas-apr2024">RakuAST</a>. This mammoth task started previously by <a href="https://jnthn.net/">Jonathan Worthington</a>. In the time since his award of the grant, he has made 823 commits to RakuAST, and his overall contribution to Raku in the past couple of years is second only to the very prolific <a href="https://github.com/lizmat">Elizabeth Mattijsen</a>. His contributions can be viewed on <a href="https://github.com/rakudo/rakudo/commits?author=niner">github</a>. It is impossible to describe all his activity with this project, and I imagine it will have taken much more than the 200 hours he had thought it would take in his original application. His <a href="https://niner.name/blog/rakuast_grant_report/index.html">commentary</a> on the project is available on his own <a href="https://niner.name/blog">blog pages</a> which also contains other interesting stuff. A summary of key activities can be extracted from <a href="https://rakudoweekly.blog/blog-feed/">Rakudo Weekly Blogs</a> by Elizabeth, and these are shamelessly reproduced in reverse chronological order with links to the original blog pages, as they are representative of the vast scope of his work : -</p> <h4><a href="https://rakudoweekly.blog/2025/03/25/2025-12-red-on-rakuast/">2025-12</a></h4> <p>Stefan Seifert basically concluded [his] work on the Raku bootstrap, with the number of test-files passing equalling the number of passing test-files in the non-bootstrapped Rakudo.</p> <p>The number of passing test-files with the new Raku grammar are now 141/153 (make test +0) and 1299/1345 (make spectest +20).</p> <h4><a href="https://rakudoweekly.blog/2025/03/17/2025-11-cuddlies-for-sale/">2025-11</a></h4> <p>Stefan Seifert fixed a potential segfault in generating object IDs, and an issue with signatures containing multiple slurpies, and an issue with the will trait.</p> <p>Stefan Seifert started focusing on bootstrapping the new Raku grammar from scratch (whereas until now it assumed there was a working Raku available) as opposed to try fixing errors in roast. This work is available in a branch as of this writing, and the number of passing spectest files in this fully bootstrapped implementation of the Raku Programming Language is now already 1228 (out of 1345, as opposed to 1279 in the non-bootstrapped version). Another major step forward to making RakuAST mainstream!</p> <p>Stefan Seifert also fixed quite a few issues (and that’s an understatement!) in the non-bootstrapped RakuAST as well.</p> <h4><a href="https://rakudoweekly.blog/2025/03/10/2025-10-final-cfp-week/">2025-10</a></h4> <p>Stefan Seifert continued working on RakuAST. The most significant fixes:* BEGIN time call for non-simple constructs* support for %?RESOURCES and $?DISTRIBUTION* blocks as defaults for parameters* many attribute and package stub issues* added several warnings* and many smaller fixes!</p> <h4><a href="https://rakudoweekly.blog/2025/03/03/2025-09-counting-down/">2025-09</a></h4> <p>Stefan Seifert continued working on RakuAST. The most significant fixes:* operators / terms defined as variables* return with pair syntax* several variable visibility issues at BEGIN time* fixes to ss/// and S//* several (sub-)signature and generics issues* binding attributes in method arguments* several issues related to categoricals* support <|c> and <|w> assertions in regexes* several return issues / return value issues* progress in making require work* and many, many, many more smaller fixes!</p> <h4><a href="https://rakudoweekly.blog/2025/02/24/2025-08-starting-an-avalanche/">2025-08</a></h4> <p>Stefan Seifert continued working on RakuAST. The most significant fixes:* non-trivial lazy loops* allow declaration of $_ in loops and other loop related fixes* handling labels with loop structures* a large number of regex related features, such as fixing LTM (Longest Token Match) matching and interpolation of attributes in regexes* exceptions thrown in CHECK phasers* support added for tr/// and TR///* better handling of subroutine stubs* and many, many more smaller fixes!</p> <h4><a href="https://rakudoweekly.blog/2025/02/17/2025-07-unexpected-quora/">2025-07</a></h4> <ul><li>pointy blocks with loop modifiers</li><li>quite a lot of (nested) thunk / block related issues</li><li>post constraints on non-subset type parameters</li><li>exceptions in .ACCEPTS at compile time</li><li>fixed implicits such &?ROUTINE in methods</li><li>fixed labels on lazy loops</li><li>several regex related issues</li><li>and many more smaller fixes!</li></ul> <h4><a href="https://rakudoweekly.blog/2024/09/02/2024-36-on-top/">2024-36</a></h4> <p>Stefan Seifert continued working on RakuAST and fixed some more issues with the phasers, multi-part named roles, language versions, where clauses on subsets and much more!</p> <h4><a href="https://rakudoweekly.blog/2024/08/26/2024-35-cro-%f0%9f%92%8d-htmx/">2024-35</a></h4> <p>Stefan Seifert continued working on RakuAST and fixed issues with the will trait, CHECK phasers, the use variables pragma, multi regexes and much more!</p> <h4><a href="https://rakudoweekly.blog/2024/08/19/2024-34-steaming-ahead/">2024-34</a></h4> <p>Stefan Seifert continued working on RakuAST and produced more than 50 commits, fixing all of the remaining S03 tests and other issues.</p> <h4><a href="https://rakudoweekly.blog/2024/08/12/2024-33-p6c-ending/">2024-33</a></h4> <p>Stefan Seifert changed the behaviour of throws-like (for the better) in light of compilation errors.Stefan Seifert continued working on RakuAST, fixing: error messages, operator properties on custom operators, several meta-operator and hypering issues, dispatch using .?, .+ and .*, adverbs on infixes, and more.</p> <h4><a href="https://rakudoweekly.blog/2024/08/05/2024-32-de-python/">2024-32</a></h4> <p>Stefan Seifert returned to RakuAST development and completed the work on the branch that took a new approach to compile time actions (really a GBR aka Great BEGIN Refactor). A branch that was started by Jonathan Worthington over a year ago. Stefan continued from there by fixing use fatal.</p> ]]> </content></entry><entry> <title>PEVANS Core Perl 5: Grant Report for March 2025</title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/pevans_core_dev_march_2025"/> <id>tag:news.perlfoundation.org,2025-04-16:/post/pevans_core_dev_march_2025</id> <published>2025-04-16T07:27:34</published> <updated>2025-04-16T07:27:34</updated> <summary> <![CDATA[ Paul writes: Hours: 4.5 SV vstring API https://github.com/Perl/perl5/pull/23075 1.5 PERL_MAGIC_env independence in hv.c https://github.com/Perl/perl5/pull/23076 4 HvSTASHAUX https://github.com/leonerd/perl5/tree/hv-stashaux 3 Rename `any` and `all` features https://github.com/Perl/perl5/pull/23105 Total: 13 hours ]]> </summary> <author> <name>alh</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Paul writes:</p> <p>Hours:</p> <ul><li>4.5 = SV vstring API<ul><li>https://github.com/Perl/perl5/pull/23075</li></ul></li><li>1.5 = PERL_MAGIC_env independence in hv.c<ul><li>https://github.com/Perl/perl5/pull/23076</li></ul></li><li>4 = HvSTASHAUX<ul><li>https://github.com/leonerd/perl5/tree/hv-stashaux</li></ul></li><li>3 = Rename <code>any</code> and <code>all</code> features<ul><li>https://github.com/Perl/perl5/pull/23105</li></ul></li></ul> <p>Total: 13 hours</p> ]]> </content></entry><entry> <title>Perl Community Roundtable -- Meeting Notes for March 2025</title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/perl-community-roundtable-march-2025"/> <id>tag:news.perlfoundation.org,2025-04-03:/post/perl-community-roundtable-march-2025</id> <published>2025-04-03T20:02:12</published> <updated>2025-04-03T20:02:12</updated> <summary> <![CDATA[ The Perl Community Roundtable met on March 21, via Zoom, and the following discussions were presented: Remembrance The Community Roundtable took a moment to remember Andrew Main and discussed his contributions to the Perl community over many years. North American Conference Planning Ruth Holloway, Conference Chair Planning for the 2025 TPRC is well underway; speaker selection is almost completed, and registration is open now at Eventbrite. The conference will be ]]> </summary> <author> <name>D Ruth Holloway</name> </author> <category term="Meetings" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <p>The Perl Community Roundtable met on March 21, via Zoom, and the following discussions were presented:</p> <h2>Remembrance</h2> <p>The Community Roundtable took a moment to remember Andrew Main (ZEFRAM), and discussed his contributions to the Perl community over many years.</p> <h2>North American Conference Planning -- Ruth Holloway, Conference Chair</h2> <p>Planning for the 2025 TPRC is well underway; speaker selection is almost completed, and registration is open now at <a href="https://www.eventbrite.com/e/the-perl-raku-conference-in-greenville-sc-2025-tickets-1029312049047">Eventbrite</a>. The conference will be held June 27-29, at the Holiday Inn Express and Suites in Greenville, South Carolina. </p> <h2>Toronto Perl Mongers -- Olaf Alders</h2> <p>The Toronto Perl Mongers will be hosting a talk online by Dave Cross, and is planning for similar high-profile talks in the future. The previous such event in December with Randal Schwartz was considered a huge success, and raised a good bit of money for TPRF and raised the profile on the Toronto Perl Mongers.</p> <h2>Mongueurs de Perl -- Emmanuel Seyman</h2> <p>Emmanuel is currently the president of the Mongueurs de Perl, which promotes Perl in French-speaking countries, particularly in France. The nonprofit organization has been briskly busy in the last year or so, including helping with organizing this year's Perl Toolchain Summit in Leipzig, Germany. They do a lot, and with very few people. The Mongueurs could use more folks helping them in their mission, particularly in the Francophone world outside France.</p> <h2>Perl Ads platform -- Olaf Alders</h2> <p>Dave Cross has created a simple advertising platform that MetaCPAN and others are using to publish advertisements. It is easily modified with a pull request on the JSON file of ads in <a href="https://github.com/PerlToolsTeam/perl-ads">Dave's repository</a>.</p> <h2>Perl Toolchain Summit -- Philippe Bruhat</h2> <p>Philippe is an organizer in this year's summit, and stressed the importance of including new people who are interested in projects at every level. He pointed out that he has made a point of inviting at least a few new attendees at each summit going forward, when interest in a toolchain project has been expressed. Getting folks interested in our projects--via this meeting and other venues--is a good way to grow our project teams and allow long-time members to rotate off of those projects when they desire. </p> <h2>Dancer2 -- Ruth Holloway</h2> <p>The Dancer2 project has recently completed a grant to revise the documentation for Dancer2, and the team is finishing up final edits there. Fresh activity on Dancer2 in the last year or so attracted the attention of the original author, Alexis Sukrieh, who has released a new "LiteBlog" plugin for Dancer2. </p> <h2>TPRF Board -- Ruth Holloway and Bruce Gray</h2> <p>Bruce has recently taken over the role of Secretary of the Foundation, after the departure of Makoto Nozaki, who had served in that role for several years.</p> <h2>Contributions to the Community</h2> <p>While companies that make financial contributions, either via the conferences, the Mongueurs de Perl, or the TPRF, are absolutely appreciated, all of our organizations and major projects definitely need to make that appreciation much louder, which encourages further donations both by that company, and others.</p> <p>Additionally, we discussed ways that companies could contribute to the success of projects in the Perl and Raku ecosystems by donating time for their employees, particularly to work on modules and projects that are of use to them. In some countries (including the USA), this can be considered "research and development" time, which may be leverageable in a company tax statement. Alternatively, it can be presented as an in-kind contribution to the non-profit organization in our ecosystem, and become tax-deductible in that way. Either way, companies should definitely contact the non-profits they wish to support in this way, to receive proper credit and documentation, as well as the non-profit's public gratitude for their contribution. </p> <h2>Meta-discussion on the Community Roundtable</h2> <p>It has been the case for many years that groups of people are working on projects (and for companies) using Perl without knowledge of any other "islands" of Perl activity; the example of Koha was given--Ruth did not even know about the larger community until she'd been working on Koha for several years, and convinced her boss to send her to her first YAPC (Madison 2012), where many folks had not even heard of Koha! The focus of the Community Roundtable going forward is on connecting these islands of activity--this encourages participation by folks on similar projects, and a synergy of support and expertise that is available throughout the community. This Roundtable is one such way to connect the dots, globally, and will continue.</p> <p>The next Perl Community Roundtable will be held on Friday, April 18, at 1730 UTC, via <a href="https://us02web.zoom.us/j/82038746662?pwd=X1r8Tfbcq621t0LA3NbpLebmGMOhK3.1">Zoom</a>, and all interested people are welcome, and encouraged to attend.</p> ]]> </content></entry><entry> <title>TPRF Announces Monthly Community Roundtable</title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/tprf-community-roundtable"/> <id>tag:news.perlfoundation.org,2025-03-19:/post/tprf-community-roundtable</id> <published>2025-03-19T11:52:12</published> <updated>2025-03-19T11:52:12</updated> <summary> <![CDATA[ For some time now, the TPRF has hosted a monthly "Communities and Reps" meeting, when bits of the community could get together and talk about what's going on in our diverse group of subcommunities. Beginning this week, we're expanding on this meeting, and turning it into the "Community Roundtable." Join us this Friday, 21 March, at 1730 UTC, via Zoom. Why Should I Attend? We hear it all the time ]]> </summary> <author> <name>D Ruth Holloway</name> </author> <category term="Meetings" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <p>For some time now, the TPRF has hosted a monthly "Communities and Reps" meeting, when bits of the community could get together and talk about what's going on in our diverse group of subcommunities. Beginning this week, we're expanding on this meeting, and turning it into the "Community Roundtable." Join us this Friday, 21 March, at 1730 UTC, via <a href="https://us02web.zoom.us/j/82038746662?pwd=X1r8Tfbcq621t0LA3NbpLebmGMOhK3.1">Zoom</a>. </p> <h1>Why Should I Attend?</h1> <p>We hear it all the time in the press: "Perl is dead..." but as we in the community know, it's not! There are numerous busy subcommunities of both Perl and Raku, doing fantastic things for and with the languages. This meeting is your chance as a group to shout out to the world about what's going on, and seek out like-minded people who might be able to help grow your group.</p> <p>Who should attend:* You are working on a Perl or Raku project, and want to brag about it, and/or recruit new team members!* You're a member of a Perl Mongers group, and have a meeting coming up you'd like to announce!* You work for a company that uses Perl or Raku, and you're hiring!* You want to be informed about any of these things going on in the Perl and Raku ecosystem!</p> <h1>How's it work?</h1> <p>As the Chair of Community Engagement for the Foundation, I'll be moderating; if you'd like to get a spot for an announcement, just hit me up in the chat, or ahead of time on the #community-roundtable channel on the TPRF slack. Each participating group will have five minutes (I'll be timing it!) to speak out about what's going on in their group, and then we have a short bit for questions to that speaker, just one or two quick ones, then move on to the next. Each community group should focus their announcement by answering these four questions:</p> <ol><li>What's going on in your group?</li><li>What's the next big thing coming up for your group?</li><li>Are you looking for new participants in your project? If so, are you looking for any specialists (docs, XS code, whatever)?</li><li>How do I get in touch with the group to find out more or join in?</li></ol> <p>Companies announcing hiring will be at the end of the meeting; you'll have five minutes, too, and should make sure you inform us about the role you're hiring, whether or not it is remote or restricted to citizens of any country, and how to get in touch with the company.</p> <p>The meeting will be recorded, and I'll be posting a summary over the weekend following, so folks who didn't attend can find out about your announcements.</p> <p>So join us this Friday, 21 March, and the third Friday of every month at 1730 UTC on <a href="https://us02web.zoom.us/j/82038746662?pwd=X1r8Tfbcq621t0LA3NbpLebmGMOhK3.1">Zoom</a>. If you'd like to find out more, catch me online in the TPRF Slack, by messaging GeekRuthie on irc.perl.org or libera.chat, or @geekruthie:nerdch.at on Matrix!</p> ]]> </content></entry><entry> <title>Maintaining Perl (Tony Cook) January 2025</title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_tonyc_january_2025"/> <id>tag:news.perlfoundation.org,2025-03-16:/post/maintaining_perl_tonyc_january_2025</id> <published>2025-03-16T21:06:04</published> <updated>2025-03-16T21:06:04</updated> <summary> <![CDATA[ Tony writes: 2025/01/06 Monday 0.67 #22695 testing, follow-up 0.43 github notifications 0.75 #22804 research and comment 0.22 #22824 research and comment 1.08 #22882 research and comment 1.18 #22883 review discussion, work on test code 4.33 2025/01/07 Tuesday 0.25 #22888 testing and comment 0.08 #22868 briefly comment 0.33 #22864 review and approve 0.20 #22865 review and approve 0.38 #22889 ]]> </summary> <author> <name>alh</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Tony writes:</p> <p>```[Hours] [Activity]2025/01/06 Monday 0.67 #22695 testing, follow-up 0.43 github notifications 0.75 #22804 research and comment 0.22 #22824 research and comment 1.08 #22882 research and comment</p> <h1> 1.18 #22883 review discussion, work on test code</h1> <p>4.33</p> <p>2025/01/07 Tuesday 0.25 #22888 testing and comment 0.08 #22868 briefly comment 0.33 #22864 review and approve 0.20 #22865 review and approve 0.38 #22889 review and ask the OP in #22882 to test it 0.23 #22890 review and approve 0.40 #22881 review and comment</p> <h1> 0.93 #22888 research, testing, comment</h1> <p>2.80</p> <p>2025/01/08 Wednesday 0.42 github notifications 0.37 cygwin: look at disabling tests failing due to upstream bug for now, but not practical for now 0.28 #22823 review updates and comment 1.28 #22635 apply to blead, work on a perldelta, make #22894 0.28 #22880 review and comment</p> <h1> 0.95 #22883 comment</h1> <p>3.58</p> <p>2025/01/09 Thursday 1.07 #22897 review (already approved), testing 0.82 #22812 review and comments 0.07 #22824 re-check and apply to blead 1.20 #22883 re-work test code, make the fix, testing, push for CI 0.47 try to reproduce gcc warnings 0.22 #22899 review and comment on a comment 0.12 #22900 review and approve</p> <h1> 0.35 #22896 review and approve with comment</h1> <p>4.32</p> <p>2025/01/13 Monday 0.17 work on change to disable cygwin in CI for now, push for CI 0.12 #22882 follow-up 0.28 #22785 review updates and approve 0.28 #22899 review updates and approve 0.67 fix a warning from the cop_features update, and another and push for CI 0.53 #22883 check CI results, work on a perldelta, push and make PR 1.35 #22904 review</p> <h1> 0.92 #22904 more review</h1> <p>4.32</p> <p>2025/01/14 Tuesday 1.12 look at new coverity scan reports 0.77 #22904 more review 0.10 #22909 review and approve</p> <h1> 1.17 #22904 more review</h1> <p>3.16</p> <p>2025/01/15 Wednesday 0.73 #22906 comment 0.13 #22911 review, no new comments 0.23 #22910 review and comment</p> <h1> 1.53 #22904 more review</h1> <p>2.62</p> <p>2025/01/16 Thursday 2.20 #22902 research, build a tool and comment 0.33 #22819 review and approve 0.12 cop_feature warning: check CI results, toke.c warning already fixed, rebase, push and make PR 22920</p> <h1> 1.93 #22904 finish review, a few comments</h1> <p>4.58</p> <p>2025/01/20 Monday 0.15 #22904 review updates and approve 0.18 #22920 apply to blead 1.67 #22881 more review, more comments 0.68 #22623 comment 0.23 #22932 review and comment 0.40 #22933 review and comments</p> <h1> 1.28 #22892 debugging, research</h1> <p>4.59</p> <p>2025/01/21 Tuesday 0.17 #22933 review updates and approve 0.23 #p5p discussion re calls to undeclared functions 0.45 #22932 review updates and follow-up comment 0.25 #22930 review and comment 0.13 #22932 review updates and approve</p> <h1> 0.73 #21877 debugging</h1> <p>1.96</p> <p>2025/01/22 Wednesday 0.87 #22937 comment 0.28 #22906 review updates and approve 0.42 coverity scan results 0.17 #22812 review updates and mark several comments resolved 1.70 #21877 debugging, looks like a CoW refcnt issue when</p> <h1> copying into the same SV twice, need more debugging</h1> <p>3.44</p> <p>2025/01/23 Thursday 0.12 #22931 review and approve 0.28 #22927 review and comment 2.28 #21877 more debugging 1.75 #21877 more debugging, looks like pp_subst vs sv_uncow_flags and SV_COW_DROP_PV, try to make a simple</p> <h1> reproducer</h1> <p>4.43</p> <p>2025/01/28 Tuesday 0.18 #22812 review updates and approve 1.48 #22927 review and comments 0.52 #22907 rebase, testing, push for CI 1.77 #21877 try to make it leak without code change, work up a</p> <h1> fix anyway and push for CI</h1> <p>3.95</p> <p>2025/01/29 Wednesday 0.32 #22945 review and approve 0.13 #22946 review and comment 0.32 #22947 review and approve 0.10 #22948 review, restart mingw64 CI 0.18 test if cygwin works again (3.5.6 released) - push for CI 0.27 check CI results, make PR 22951 0.28 #22949 review and approve 0.13 #22950 review and approve</p> <h1> 2.07 #22942 review, testing, comments</h1> <p>3.80</p> <p>2025/01/30 Thursday 0.32 #22907 follow-up comment 0.18 #22953 review and approve 0.25 #22948 review and approve 0.62 #22940 review and approve</p> <h1> 0.92 #21877 try to reproduce failed CI run, debugging</h1> <p>2.29</p> <p>2025/01/31 Friday</p> <h1> 0.20 #21877 comment with an update</h1> <p>0.20</p> <p>Which I calculate is 54.37 hours.</p> <p>Approximately 48 tickets were reviewed or worked on, and 3 patcheswere applied.```</p> ]]> </content></entry><entry> <title>Maintaining Perl (Tony Cook) December 2024 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_tonyc_december_2024"/> <id>tag:news.perlfoundation.org,2025-03-16:/post/maintaining_perl_tonyc_december_2024</id> <published>2025-03-16T20:56:05</published> <updated>2025-03-16T20:56:05</updated> <summary> <![CDATA[ Tony writes: 2024/12/02 Monday 0.18 github notifications 0.70 #22773 review updates, testing and approve 0.15 #22792 look over test failures, comment 0.30 #22788 rebase. squash and push for CI 0.38 #22799 review, research, comment and approve 0.33 #22795 review and approve 0.65 #22797 review and approve, research and comment 0.18 #22792 follow-up 0.22 #22784 review CI, apply to blead, perldelta ]]> </summary> <author> <name>alh</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Tony writes:</p> <p>```[Hours] [Activity]2024/12/02 Monday 0.18 github notifications 0.70 #22773 review updates, testing and approve 0.15 #22792 look over test failures, comment 0.30 #22788 rebase. squash and push for CI 0.38 #22799 review, research, comment and approve 0.33 #22795 review and approve 0.65 #22797 review and approve, research and comment 0.18 #22792 follow-up 0.22 #22784 review CI, apply to blead, perldelta 0.23 #22790 review and approve</p> <h1> 1.15 #22785 review</h1> <p>4.47</p> <p>2024/12/03 Tuesday 0.93 #22785 more review 0.32 #22805 review, research and approve 0.18 github notifications 0.93 #20060 discussion on #p5p 1.75 #22806 work on a fix, push for CI, try to get the build to fail on FreeBSD, ask cguevara about his builds, try to</p> <h1> reproduce build failures</h1> <p>4.11</p> <p>2024/12/04 Wednesday 0.45 #22785 research and follow-up comment 0.08 #22807 review feedback and apply to blead 0.35 #22638 follow-up 0.25 #22809 review and approve 0.28 #22810 review and comment 0.90 #22811 review, testing and comment 0.35 #22811 work up a crashing case, comment 0.28 #22812 review and comment 0.17 #22813 review and approve 0.20 #22814 review and approve</p> <h1> 1.22 #22797 benchmarking and comment</h1> <p>4.53</p> <p>2024/12/05 Thursday 0.20 github notifications 0.10 #22810 review update and approve 0.85 #22815 review and approve 2.22 re-work cop_features to support more feature bits</p> <h1> 1.53 more re-work cop_features, testing, open PR 22824</h1> <p>4.90</p> <p>2024/12/09 Monday 0.62 list catch up 0.57 #22785 review updates 1.23 #22695 work on a non-temporary fix for the address conflict problem 3.25 #22695 try to generalize it a bit, testing, clean up and</p> <h1> push for CI</h1> <p>5.67</p> <p>2024/12/10 Tuesday 0.53 #22695 check CI, write up a perldelta and make PR 22853 0.15 #22811 briefly comment 0.58 check coverity scan report 0.82 #22819 start review 0.18 #22819 more review and comment 0.23 #22823 review and comment 0.12 #22827 review and approve 0.50 #22843 review and approve</p> <h1> 1.80 #22125 setup, work on linking to the right lib</h1> <p>4.91</p> <p>2024/12/11 Wednesday 0.58 #22846 review, comment 1.38 #22846 more review, comment</p> <h1> 0.33 #22125 debug useshrplib too, start a build</h1> <p>2.29</p> <p>2024/12/12 Thursday 0.15 #22788 follow-up 0.27 #22823 follow-up comment 0.43 #22846 review changes and approve 1.00 #22857 testing, diagnosis, comments 0.73 #22125 clean up commit a bit, push to smoke-me</p> <h1> 0.80 #22125 check CI results, fix some issue, re-push</h1> <p>3.38</p> <p>2024/12/16 Monday 0.97 github notifications 0.15 #22589 look for the other ticket and comment 0.58 #22725 re-check updates and other comments and approve 0.52 #22745 review and approve 0.57 #22808 review and approve 0.45 #22785 review, comment 0.20 #22785 more review 1.82 #22125 comment, debugging, push updates and debug output</p> <h1> code to smoke-me</h1> <p>5.26</p> <p>2024/12/17 Tuesday</p> <h1> 0.53 #22824 read comments, fail to decide and comment</h1> <p>0.53</p> <p>2024/12/18 Wednesday 0.28 #22823 review updates and approve 0.92 #22785 more review, comment 0.85 #22854 research and comment 0.50 #22855 research and comment 0.52 #22786 review discussion, testing 0.32 #22786 more testing, briefly comment</p> <h1> 0.40 #22804 review and research</h1> <p>3.79</p> <p>2024/12/19 Thursday</p> <h1> 1.83 run API checker, security discussion with khw, debugging</h1> <p>1.83</p> <p>Which I calculate is 45.67 hours.</p> <p>Approximately 38 tickets were reviewed or worked on, and 2 patcheswere applied.</p> <p>```</p> ]]> </content></entry><entry> <title>Early Bird Registration, and the last week of the CFP!</title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/conference_update_march"/> <id>tag:news.perlfoundation.org,2025-03-06:/post/conference_update_march</id> <published>2025-03-06T15:36:02</published> <updated>2025-03-06T15:36:02</updated> <summary> <![CDATA[ Early Bird Registration remains open for the Perl and Raku Conference 2025 in Greenville, SC, at the early price of $275. Ticket prices go up to $350 on April 15, so get your tickets right away! The conference team is working hard to put together a great program of speakers to help celebrate the Perl and Raku languages. Come on down to the Palmetto State and spend time with friends ]]> </summary> <author> <name>D Ruth Holloway</name> </author> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/18b848e81e409ff9941b91c82978ca27bae49c8b/tprc2025_512x512.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Early Bird Registration remains open for the<a href="https://tprc.us"> Perl and Raku Conference 2025 in Greenville, SC</a>, at the early price of $275. Ticket prices go up to $350 on April 15, so get your tickets right away! The conference team is working hard to put together a great program of speakers to help celebrate the Perl and Raku languages. Come on down to the Palmetto State and spend time with friends and colleagues for two great days of talks on June 28 and 29, 2025! Purchase your ticket right away <a href="https://www.eventbrite.com/e/the-perl-raku-conference-in-greenville-sc-2025-tickets-1029312049047?aff=oddtdtcreator">at EventBrite</a>.</p> <p>Our pre-conference class will be led again this year by Chris Prather, whose class, <em>Going Rogue with Metamodern Perl</em>, invites developers of all backgrounds to explore indie-style game development through the lens of Perl. Look for registration details for that class on Eventbrite soon. The class will be held on Friday, June 27, from 9-5, and lunch will be provided.</p> <p>Speaking of speakers, you've been thinking of submitting a talk, haven't you? But in a true Perl community tradition, you've waited until the last minute to write up your idea and submit it, haven't you? Well, we're here to tell you that the last minute is indeed upon us! The CFP will close on March 15, a little over a week away! <a href="https://www.papercall.io/tprcgsp2025">Submit your session on PaperCall</a> right away! If your talk is accepted, your admission to the conference will be <strong>free!</strong> </p> ]]> </content></entry><entry> <title>Grant Report: Raku Ecosystem Final</title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/raku-ecosystem-tonyo-final"/> <id>tag:news.perlfoundation.org,2025-03-05:/post/raku-ecosystem-tonyo-final</id> <published>2025-03-05T09:22:35</published> <updated>2025-03-05T09:22:35</updated> <summary> <![CDATA[ Tony O'Dell has been working on a modernised and well documented Ecosystem management platform `zeco`. This is complex work that integrates contributor management and distro management, and is a vital cog in the evolution of a programming language and its accessibilty to its users. The handling of updates and secure,reliable, reproducible access to distros underpins the sustainable viability of such a platform. It was supported by this grant. Key to ]]> </summary> <author> <name>Saif Ahmed</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Raku Development" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Raku Foundation" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/dd1e1502cab5d5bed742159522782a6266699f5d/Raku Infrastructure.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Tony O'Dell has been working on a modernised and well documented Ecosystem management platform <code>zeco</code>. This is complex work that integrates contributor management and distro management, and is a vital cog in the evolution of a programming language and its accessibilty to its users. The handling of updates and secure,reliable, reproducible access to distros underpins the sustainable viability of such a platform. It was supported by <a href="https://news.perlfoundation.org/post/raku-ecosystem-tonyo">this grant</a>. Key to this project is documentation as well as the underlying secure infrastructure, and these have been a significant ongoing activity. </p> <p><img src="https://news.perlfoundation.org/post/_ra-rel-mnt_/simplecas/fetch_content/dd1e1502cab5d5bed742159522782a6266699f5d/Raku%20Infrastructure.png" alt="" /></p> <h3>9th September 2024</h3> <p>Making good progress. User/group, and dist management are all in place. Tests are written and everything is working as intended when used in a specific way. More tests are incoming to ensure corner cases and dist name collisions are handled gracefully as well as some configuration options to make private ecosytems more maintainable. Below are the individual updates per grant point, ugexe is currently reviewing the bits marked below as feature complete so hopefully next update they'll be marked as done.</p> <ul><li>ERD - schema is in place and being used. The migration mechanism for schema changesis in place and being used to manage those changes as necessary during development.</li><li>General Configuration - mostly in place. The upload mechanism for uploaded distsis currently set to use an AWS bucket, this will likely change to allow ecosystemsto use a custom command to manage how and where uploaded dists end up with the most flexibility.</li><li>User management - feature complete. Currently being reviewed by ugexe for completeness</li><li>Group/role management - same as #3</li><li>Dist management modules - mostly feature complete, pending the custom uploadcommand. Being reviewed by ugexe for completness.</li><li>Create ingestion modules for dists - feature complete. This is handled realtime now with #5, users will no longer need to wait for a dist processor toinspect and index files.</li><li>Ecosystem META6.json & binary index endpoints- feature complete. Currently beingreviewed by ugexe for completeness. Initial benchmarks for the binary index arelooking very nice (bst = binary index search, grp = post-processed json META search):</li></ul> <p>PARTIAL MATCH:Benchmark:</p> <p>```Timing 50 iterations of bst, grp... bst: 5.107 wallclock secs (5.078 usr 0.112 sys 5.190 cpu) @ 9.791/s (n=50) (warning: too few iterations for a reliable count) grp: 33.074 wallclock secs (31.703 usr 1.400 sys 33.103 cpu) @ 1.512/s (n=50) (warning: too few iterations for a reliable count)O-----O--------O------O------O| | Rate | bst | grp |O=====O========O======O======O| bst | 9.79/s | -- | -85% || grp | 1.51/s | 548% | -- |O-----O--------O------O------O</p> <p>EXACT:Benchmark:Timing 50 iterations of bst, grp... bst: 0.076 wallclock secs (0.102 usr 0.036 sys 0.138 cpu) @ 658.293/s (n=50) (warning: too few iterations for a reliable count) grp: 37.780 wallclock secs (36.596 usr 1.247 sys 37.844 cpu) @ 1.323/s (n=50) (warning: too few iterations for a reliable count)O-----O--------O--------O-------O| | Rate | bst | grp |O=====O========O========O=======O| bst | 658/s | -- | -100% || grp | 1.32/s | 50252% | -- |O-----O--------O--------O-------O```</p> <h3>January 30 2025 update</h3> <p>Been a little bit slow since the last update but we're wrapping it up. The code is complete, the docs are complete, and this is being used gradually for migrating the current ecosystem. Since the last update I have:</p> <ul><li>Completed the docs, they're now in final form for release</li><li>Communicated the existence and other information about the ecosystem code to the raku community</li><li>Fixed some minor bugs related to config and dist ingestion</li><li>Added hooks for post dist processing to allow for flexibility in dist storage and emails</li></ul> <p>At this time I believe this ecosystem grant is complete.</p> ]]> </content></entry><entry> <title>PEVANS Core Perl 5: Grant Report for February 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/pevans_core_dev_february_2025"/> <id>tag:news.perlfoundation.org,2025-03-05:/post/pevans_core_dev_february_2025</id> <published>2025-03-05T07:10:01</published> <updated>2025-03-05T07:10:01</updated> <summary> <![CDATA[ Paul writes: Hours: 4 Regexp global pos API https://github.com/Perl/perl5/pull/22971 2 `faster-signatures` parser reshaping https://github.com/Perl/perl5/pull/22967 3 Lexical method invocation operator 1 Bugfix lexical methods field/signature https://github.com/Perl/perl5/issues/23030 https://github.com/Perl/perl5/pull/23031 Total: 10 hours ]]> </summary> <author> <name>alh</name> </author> <category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/"> <![CDATA[ <img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br> <p>Paul writes:</p> <p>Hours:</p> <ul><li>4 = Regexp global pos API<ul><li>https://github.com/Perl/perl5/pull/22971</li></ul></li><li>2 = <code>faster-signatures</code> - parser reshaping<ul><li>https://github.com/Perl/perl5/pull/22967</li></ul></li><li>3 = Lexical method invocation operator (PPC0033)</li><li>1 = Bugfix lexical methods + field/signature<ul><li>https://github.com/Perl/perl5/issues/23030</li><li>https://github.com/Perl/perl5/pull/23031</li></ul></li></ul> <p>Total: 10 hours</p> ]]> </content></entry> </feed>
