This feed does not validate.
<updated>2025-10-07T18:22:57</updated>
^
line 12, column 32: (15 occurrences) [help]
<published>2025-10-07T18:22:57</published>
^
line 13, column 30: (15 occurrences) [help]
<updated>2025-10-07T18:22:57</updated>
^
In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation.
line 26, column 0: (30 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-10-07T18:22:57</updated><generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 6.2.2</generator><entry> <title>Maintaining Perl 5 Core (Dave Mitchell): September 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_dave_mitchell_september_2025"/> <id>tag:news.perlfoundation.org,2025-10-07:/post/maintaining_perl_dave_mitchell_september_2025</id> <published>2025-10-07T18:22:57</published> <updated>2025-10-07T18:22:57</updated> <summary> <![CDATA[ Dave writes: Last month I completed rewriting and modernising perlxs.pod, Perl's reference manual for XS. It's now sitting as PR #23795, and will hopefully get merged before too long. ]]> </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>Last month I completed rewriting and modernising perlxs.pod, Perl'sreference manual for XS. It's now sitting as PR <a href="https://github.com/perl/perl5/pull/23795">#23795</a>, and will hopefullyget merged before too long. (I actually completed the work two days intoOctober, so next month's report will show a few hours.)</p> <p>From the PR's description:</p> <p>This branch completely rewrites and modernises the XS reference manual,perlxs.pod.</p> <p>The new file is about twice the size of the old one.</p> <p>This branch:</p> <ul><li>deletes some obsolete sections;</li><li>reorders the existing sections into a more logical order;</li><li>adds a large new introductory/overview part, which explainsall the background needed to understand what XSUBs do, includingSVs, the stack, reference counts, magic etc.</li><li>includes a BNF syntax section</li><li>modernises: e.g. it uses ANSI parameter syntax throughout</li><li>has a fully-worked example using T_PTROBJ</li></ul> <p>SUMMARY:</p> <ul><li>23:19 modernise perlxs.pod</li><li><p>3:50 rationalise XS typemap file search order</p> <p>Total:</p> <ul><li>27:09 (HH::MM)</li></ul></li></ul> ]]> </content></entry><entry> <title>Maintaining Perl (Tony Cook) September 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_tonyc_september_2025"/> <id>tag:news.perlfoundation.org,2025-10-07:/post/maintaining_perl_tonyc_september_2025</id> <published>2025-10-07T18:15:54</published> <updated>2025-10-07T18:15:54</updated> <summary> <![CDATA[ Tony writes: 2025/09/01 Monday 0.48 #23641 testing, comment 0.77 #23659 review and comment 0.20 #23659 review updates and comment 0.83 reply DB.pm discussion 0.25 #23648 try to reproduce and comment 0.47 #23659 review and approve 3.00 2025/09/02 Tuesday 0.60 #23627 follow-up, review and comment 0.53 #23616 research and comment 0.23 #23669 review, look for a similar test, comment 0.43 ]]> </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/09/01 Monday 0.48 #23641 testing, comment 0.77 #23659 review and comment 0.20 #23659 review updates and comment 0.83 reply DB.pm discussion 0.25 #23648 try to reproduce and comment</p> <h1> 0.47 #23659 review and approve</h1> <p>3.00</p> <p>2025/09/02 Tuesday 0.60 #23627 follow-up, review and comment 0.53 #23616 research and comment 0.23 #23669 review, look for a similar test, comment 0.43 #23641 testing, follow-up 0.32 #23648 follow-up 0.32 #23667 review, comment 0.57 #23668 review, testing, comment and approve</p> <h1> 0.85 #13307/#23661 testing, comment on both</h1> <p>3.85</p> <p>2025/09/03 Wednesday 0.12 #23668 review updates and reapprove 0.57 #23661 review discussion and consider, request changes 0.18 #23616 review and approve 0.33 #23627 review updates and approve</p> <h1> 0.62 #23669 testing and comments</h1> <p>1.82</p> <p>2025/09/04 Thursday 0.15 #23661 review changes, test results and comment 1.07 #23573 testing, approve with comment 0.13 #23669 review updates and approve 0.52 #23641 review, research and comment 0.15 #23638 check latest changes and approve 0.37 #23680 review and approve 0.17 #23680 review updates and still approved 0.18 #23682 review, check test failures and comment</p> <h1> 0.33 #23679 review</h1> <p>3.07</p> <p>2025/09/05 Friday</p> <h1> 0.42 #23680 follow-up</h1> <p>0.42</p> <p>2025/09/08 Monday 1.07 #23641 review, research, comments 0.08 #23670 review and approve 0.55 #23671 review, research and approve with comment 0.08 #23672 review and approve 0.18 #23678 review and comment 0.22 #23683 review and comment</p> <h1> 2.62 test_pl.pod - make a start</h1> <p>4.80</p> <p>2025/09/09 Tuesday 0.82 #23679 review and comment 1.48 test_pl.pod - more</p> <h1> 1.78 test_pl.pod - more</h1> <p>4.08</p> <p>2025/09/10 Wednesday 1.30 #23690 review, testing and comment 0.15 #23691 review and approve 0.70 #23694 review and approve</p> <h1> 1.42 test_pl.pod - mostly done, needs review</h1> <p>3.57</p> <p>2025/09/11 Thursday 0.48 #23695 review and comment 0.12 #23696 review and approve 0.10 #23697 review and approve 1.48 #23698 review and comments</p> <h1> 1.38 test_pl.pod, add and test example, make PR 23700</h1> <p>3.56</p> <p>2025/09/15 Monday 0.25 #23700 follow-up 1.57 #23690 review updates, testing, research and comment 0.32 #23695 review updates and approve 1.00 #23641 testing, research and comment</p> <h1> 0.92 test_pl.pod - some missing stuff, don’t talk about TAP</h1> <p>4.06</p> <p>2025/09/16 Tuesday 0.42 #23698 review updated PR and approve 0.73 test_pl.pod - minor fixes, add to podcheck 0.28 #23678 review and comment 0.80 #23702 review</p> <h1> 0.92 #23702 try to understand line-breaking</h1> <p>3.15</p> <p>2025/09/17 Wednesday 0.17 #23702 comment 1.50 #23678 try to understand the threads watchdog 1.00 #23678 debugging, testing and comment</p> <h1> 0.65 #23715 review and comments</h1> <p>3.32</p> <p>2025/09/18 Thursday 0.12 #23717 review and approve 0.27 #23718 review and approve 0.42 #23719 review and approve 0.32 #23720 review, research and comment 0.17 #23721 review and approve 0.52 #23714 review, research and comment 0.42 #23720 research and follow-up</p> <h1> 1.48 test.pl/test-dist-modules.pl clean up, testing, fixes</h1> <p>3.72</p> <p>2025/09/22 Monday 0.42 #23720 review updates and approve 0.22 #23714 comment 0.63 #23747 review and comment 0.58 #23731 review and comment 0.52 #23730 review, research and comment 0.72 #23728 review, research and comments 0.12 #23734 review and approve 0.13 #23735 review and approve 0.15 #23736 review and approve with comment 0.33 #23742 review and approve 0.42 #23743 review and approve 0.13 #23749 review and approve</p> <h1> 0.12 #23746 review and approve</h1> <p>4.49</p> <p>2025/09/23 Tuesday 0.70 #23731 review updates and approve 0.25 #23752 review and comment 0.32 #23754 review and approve 0.22 #23747 review update and approve 0.17 #23725 review and briefly comment</p> <h1> 0.27 #23752 review update and comment</h1> <p>1.93</p> <p>2025/09/24 Wednesday 0.82 #23710 review and approve 0.25 #23076 review discussion and change and approve 0.83 #23761 review, research and approve 1.22 #23753 look into CI failure, testing, fixes start a full test 0.28 #23753 clean up and push to PR for CI</p> <h1> 0.37 #23757 review and approve</h1> <p>3.77</p> <p>2025/09/25 Thursday 0.60 github notifications 0.23 #23753 comment and approve 1.05 #23759 review, check cpan, testing, approve with comment 0.17 #23763 review and comment 0.08 #23765 review and approve 0.08 #23766 review and approve 0.08 #23767 review and comment 0.82 #21877 write tests, work on re-work</p> <h1> 0.45 #21877 more re-work</h1> <p>3.56</p> <p>2025/09/29 Monday</p> <h1> 3.27 #23641 review, testing</h1> <p>3.27</p> <p>2025/09/30 Tuesday 1.28 #23782 review and comments 0.35 #23779 review and approve</p> <h1> 0.63 #23641 more testing and comment</h1> <p>2.26</p> <p>Which I calculate is 61.7 hours.</p> <p>Approximately 63 tickets were reviewed or worked on.```</p> ]]> </content></entry><entry> <title>PEVANS Core Perl 5: Grant Report for September 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/pevans_core_dev_september_2025"/> <id>tag:news.perlfoundation.org,2025-10-07:/post/pevans_core_dev_september_2025</id> <published>2025-10-07T18:06:27</published> <updated>2025-10-07T18:06:27</updated> <summary> <![CDATA[ Paul writes: This month I spent mostly tidying up various bits of fallout from last month's `OP_MULTIPARAM` work towards signatures, and also got the named parameters branch ready for review and merge, along with a few other bugfixes. 1 BBC ticket `meta` https://github.com/Perl/perl5/issues/23675 2 Bugfix `parse_subsignature on empty parens https://github.com/Perl/perl5/issues/17689 2 BBC ticket `XS-Parse-Sublike` https://github.com/Perl/perl5/issues/23674 5.5 Improvements to `B::Deparse` of on signatures https://github.com/Perl/perl5/issues/23699 https://github.com/Perl/perl5/pull/23710 1 ]]> </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>This month I spent mostly tidying up various bits of fallout from lastmonth's <code>OP_MULTIPARAM</code> work towards signatures, and also got the namedparameters branch (just-about) ready for review and merge, along with afew other bugfixes.</p> <ul><li>1 = BBC ticket <code>meta</code><ul><li>https://github.com/Perl/perl5/issues/23675</li></ul></li><li>2 = Bugfix <code>parse_subsignature()</code> on empty parens<ul><li>https://github.com/Perl/perl5/issues/17689</li></ul></li><li>2 = BBC ticket <code>XS-Parse-Sublike</code><ul><li>https://github.com/Perl/perl5/issues/23674</li></ul></li><li>5.5 = Improvements to <code>B::Deparse</code> of on signatures<ul><li>https://github.com/Perl/perl5/issues/23699</li><li>https://github.com/Perl/perl5/pull/23710</li></ul></li><li>1 = BBC ticket <code>Syntax-Keyword-MultiSub</code><ul><li>https://github.com/Perl/perl5/issues/23712</li></ul></li><li>1 = BBC ticket <code>Future-AsyncAwait</code><ul><li>https://github.com/Perl/perl5/issues/23711</li></ul></li><li>1 = Continue work on signature-named-params branch<ul><li>https://github.com/leonerd/perl5/tree/signature-named-parameters</li></ul></li><li>4 = COP warnings API additions<ul><li>https://github.com/Perl/perl5/pull/23731</li></ul></li><li>1 = BBC ticket <code>Syntax-Keyword-Try</code><ul><li>https://github.com/Perl/perl5/issues/23609</li></ul></li><li>1 = Bugfix module ends in ADJUST block<ul><li>https://github.com/Perl/perl5/issues/23758</li></ul></li><li>2 = Modernize <code>attributes.pm</code> to use v5.40<ul><li>https://github.com/Perl/perl5/pull/23769</li></ul></li><li>2 = Bugfix fieldinfo during thread cloning<ul><li>https://github.com/Perl/perl5/issues/23771</li></ul></li><li>1 = Other github code reviews</li></ul> <p>Total: 24.5 hours</p> ]]> </content></entry><entry> <title>PEVANS Core Perl 5: Grant Report for August 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/pevans_core_dev_august_2025"/> <id>tag:news.perlfoundation.org,2025-09-09:/post/pevans_core_dev_august_2025</id> <published>2025-09-09T07:41:47</published> <updated>2025-09-09T07:41:47</updated> <summary> <![CDATA[ Paul writes: In August I focused on progressing my work on sub signatures. Between the main `OP_MULTIPARAM` work and the surrounding supporting changes, we're now much better placed to look at no-snails or signatures named parameters. 17 OP_MULTIPARAM and related changes, prerequisites and post-changecleanups https://github.com/Perl/perl5/pull/23539 https://github.com/Perl/perl5/pull/23544 https://github.com/Perl/perl5/pull/23565 https://github.com/Perl/perl5/pull/23574 https://github.com/Perl/perl5/pull/23645 Total: 17 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>In August I focused on progressing my work on sub signatures. Betweenthe main <code>OP_MULTIPARAM</code> work and the surrounding supporting changes,we're now much better placed to look at no-snails or signatures namedparameters.</p> <ul><li>17 = OP_MULTIPARAM and related changes, prerequisites and post-changecleanups<ul><li>https://github.com/Perl/perl5/pull/23539</li><li>https://github.com/Perl/perl5/pull/23544</li><li>https://github.com/Perl/perl5/pull/23565</li><li>https://github.com/Perl/perl5/pull/23574</li><li>https://github.com/Perl/perl5/pull/23645</li></ul></li></ul> <p>Total: 17 hours</p> ]]> </content></entry><entry> <title>Maintaining Perl (Tony Cook) August 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_tonyc_august_2025"/> <id>tag:news.perlfoundation.org,2025-09-09:/post/maintaining_perl_tonyc_august_2025</id> <published>2025-09-09T07:39:03</published> <updated>2025-09-09T07:39:03</updated> <summary> <![CDATA[ Tony writes: 2025/08/04 Monday 0.13 github notifications 2.37 #23483 see if this can work for netbsd, testing, testing on openbsd, freebsd and comment 0.15 #23483 testing based on IRC 1.37 #23519 review, research, testing and approve 4.02 2025/08/05 Tuesday 1.33 #21877 research 1.43 #21877 work on test code 2.76 2025/08/06 Wednesday 0.47 #23503 research 0.52 #23542 review and 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:```2025/08/04 Monday 0.13 github notifications 2.37 #23483 see if this can work for netbsd, testing, testing on openbsd, freebsd and comment 0.15 #23483 testing based on IRC</p> <h1> 1.37 #23519 review, research, testing and approve</h1> <p>4.02</p> <p>2025/08/05 Tuesday 1.33 #21877 research (do I need to rewrite this?)</p> <h1> 1.43 #21877 work on test code</h1> <p>2.76</p> <p>2025/08/06 Wednesday 0.47 #23503 research 0.52 #23542 review and comment 0.43 #23539 review and approve 0.15 #23537 review and approve 0.32 #23542 review update and comment</p> <h1> 2.10 #16865 debugging</h1> <p>3.99</p> <p>2025/08/07 Thursday 0.28 #14630 testing and comment 0.08 #18786 review discussion and comment 0.38 #16808 research, testing and comment 0.42 #10376 review discussion, research and comment 0.68 #23543 review, comments 0.08 #23542 review updates and approve 0.08 #23422 apply to blead 0.18 #23459 review and approve</p> <h1> 1.37 #16865 debugging and comment</h1> <p>3.55</p> <p>2025/08/11 Monday 1.00 #23544 review and approve 0.38 #23546 review change, review history and comment 0.60 #23553 review, comments 0.47 #23555 review and comment 0.23 #23557 review and approve</p> <h1> 1.28 #16865 debugging</h1> <p>3.96</p> <p>2025/08/12 Tuesday 0.45 #23543 review discussion, research and comment 0.13 #23555 review updates and comment 0.90 #23375 review comments and long comment 0.08 #23555 review updates and approve 0.08 #23563 review and approve 0.25 #16808 comment 0.35 #10385 comment 1.27 #15004 review discussion and patch, work on an</p> <h1> alternative, testing and push for CI</h1> <p>3.51</p> <p>2025/08/13 Wednesday 0.40 github notifications 0.63 check coverity reported error and push a fix for CI 1.33 #23202 hopefully final review and comment (minor issue) 0.10 #16715 briefly research and comment 0.08 #15004 check CI, make PR 23567 0.10 coverity: check CI and make PR 23568 0.25 #15004 minor fix, testing 0.08 #23568 apply to blead</p> <h1> 1.67 #23503 review, research</h1> <p>4.64</p> <p>2025/08/14 Thursday 0.67 #23543 review updates, research and approve 0.78 #23202 review updates and comment 0.72 #23565 review and approve 0.87 #23561 research and comment</p> <h1> 0.62 #23570 review, comment, note failed CI and cause</h1> <p>3.66</p> <p>2025/08/18 Monday 0.08 #23567 review discussion, apply to blead 0.48 #23561 longish comment 1.22 #23570 review updates, struggle to understand some code, comment 0.27 #23202 review updates and approve 0.72 #23503 review, comment 0.20 #23573 comment</p> <h1> 0.57 #23553 review discussion, comment</h1> <p>3.54</p> <p>2025/08/19 Tuesday 0.62 #23533 review discussion as requested by khw, discussion with khw 0.72 check new coverity scan report</p> <h1> 1.55 #16865 debugging</h1> <p>2.89</p> <p>2025/08/20 Wednesday 0.95 #23570 review updates, research and approve 0.58 #23561 research and comments 0.97 #23574 reviewing...</p> <h1> 1.35 #23574 more reviewing</h1> <p>3.85</p> <p>2025/08/21 Thursday 1.58 #23574 more review and approve 0.60 #13140 review discussion, testing and comment 0.47 #8468 review discussion, research, testing and comment</p> <h1> 1.20 #23608 testing and comment</h1> <p>3.85</p> <p>2025/08/25 Monday 0.42 discuss handle_possible_posix with khw (while setting up to test Dennis Clark’s list reported FreeBSD failure, and testing)</p> <h1> 0.87 more FreeBSD testing, respond to Dennis</h1> <p>1.29</p> <p>2025/08/26 Tuesday 1.03 #23647 review, testing, generated code checks, comments 0.15 #23647 review update and approve 0.62 #23645 review, review CI results, testing and comment 0.43 #23644 review the involved tickets, some testing and</p> <h1> briefly comment</h1> <p>2.23</p> <p>2025/08/27 Wednesday 0.18 #16865 follow-up 0.88 #23640 review and approve 0.40 #23638 review, suggest and alternative 0.08 #23634 review and approve 0.27 #23632 review, research and comment 0.23 #23627 review and comment 0.08 #23621 review and approve 0.32 #23616 review, research and comments</p> <h1> 1.40 #16865 debugging</h1> <p>3.84</p> <p>2025/08/28 Thursday 0.60 #23654 review, research and approve 0.60 #23645 review, research, testing and approve, comment 1.15 #23641 review, testing, research and comment 0.22 #23613 review and approve 0.23 #23607 review and approve 0.48 #23612 research and comment</p> <h1> 1.27 #16865 debugging</h1> <p>4.55</p> <p>Which I calculate is 56.13 hours.</p> <p>Approximately 52 tickets were reviewed or worked on, and 3 patcheswere applied.```</p> ]]> </content></entry><entry> <title>Maintaining Perl 5 Core (Dave Mitchell): August 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_dave_mitchell_august_2025"/> <id>tag:news.perlfoundation.org,2025-09-09:/post/maintaining_perl_dave_mitchell_august_2025</id> <published>2025-09-09T07:32:26</published> <updated>2025-09-09T07:32:26</updated> <summary> <![CDATA[ Dave writes: I spent last month mainly continuing to work on rewriting and modernising perlxs.pod, Perl's reference manual for XS. The first draft is now about 90% complete. The bits that have been reworked so far have ended up having essentially none of the original text left, apart from section header titles So it's turning into a complete rewrite from scratch. It's still a work-in-progress, so nothing's been pushed yet. ]]> </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>I spent last month mainly continuing to work on rewriting and modernisingperlxs.pod, Perl's reference manual for XS. The first draft is now about90% complete. (Last month it was 80%; no doubt next month it will be 95%,then 97.5%, etc.) The bits that have been reworked so far have ended uphaving essentially none of the original text left, apart from sectionheader titles (which are now in a different order). So it's turning into acomplete rewrite from scratch.</p> <p>It's still a work-in-progress, so nothing's been pushed yet.</p> <p>During the course of writing about the XS INTERFACE keyword, I discovereda bug and fixed it; I also took the opportunity of fixing another INTERFACEbug which had been reported recently, where the C code generated wasgiving errors on recent picky C compilers.</p> <p>Summary:</p> <ul><li>12:26 fix issues with the XS INTERFACE keyword</li><li>33:58 modernise perlxs.pod</li></ul> <p>Total:</p> <ul><li>46:24 (HH::MM)</li></ul> ]]> </content></entry><entry> <title>Maintaining Perl 5 Core (Dave Mitchell): July 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_dave_mitchell_july_2025"/> <id>tag:news.perlfoundation.org,2025-08-14:/post/maintaining_perl_dave_mitchell_july_2025</id> <published>2025-08-14T04:59:41</published> <updated>2025-08-14T04:59:41</updated> <summary> <![CDATA[ Dave writes: I spent last month mainly continuing to work on rewriting and modernising perlxs.pod, Perl's reference manual for XS. The first draft is now about 80% complete. The bits that have been reworked so far have ended up having essentially none of the original text left, apart from section header titles So it's turning into a complete rewrite from scratch. It's still a work-in-progress, so nothing's been pushed yet. ]]> </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>I spent last month mainly continuing to work on rewriting and modernisingperlxs.pod, Perl's reference manual for XS. The first draft is now about80% complete. The bits that have been reworked so far have ended up havingessentially none of the original text left, apart from section headertitles (which are now in a different order). So it's turning into acomplete rewrite from scratch.</p> <p>It's still a work-in-progress, so nothing's been pushed yet.</p> <p>Other than that, I successfully diagnosed an issue where DBI was emittingwarnings on recent perls under FreeBSD.</p> <p>Summary:</p> <ul><li>7:25 GH #23306 Warnings on exit when DBI handle is global variable</li><li>34:36 modernise perlxs.pod</li></ul> <p>Total:* 42:01 (HH::MM)</p> ]]> </content></entry><entry> <title>Maintaining Perl (Tony Cook) July 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_tonyc_july_2025"/> <id>tag:news.perlfoundation.org,2025-08-11:/post/maintaining_perl_tonyc_july_2025</id> <published>2025-08-11T05:21:10</published> <updated>2025-08-11T05:21:10</updated> <summary> <![CDATA[ Tony writes: 2025/07/01 Tuesday 0.93 #23390 review behaviour, testing, review associated PR 23392 and approve 0.65 #23326 review discussion, add fix to 5.38. 5.40 votes files, mark closable with comment 0.47 #23384 review discussion, testing and comment 1.43 #23385 review and comments 3.48 2025/07/02 Wednesday 0.90 #23385 more review, comments 0.80 #23389 review 1.70 2025/07/03 Thursday 1.32 #23150 review, ]]> </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/07/01 Tuesday 0.93 #23390 review behaviour, testing, review associated PR 23392 and approve 0.65 #23326 review discussion, add fix to 5.38. 5.40 votes files, mark closable with comment 0.47 #23384 review discussion, testing and comment</p> <h1> 1.43 #23385 review and comments</h1> <p>3.48</p> <p>2025/07/02 Wednesday 0.90 #23385 more review, comments</p> <h1> 0.80 #23389 review</h1> <p>1.70</p> <p>2025/07/03 Thursday 1.32 #23150 review, review discussion, comments 0.08 #23385 brief follow-up 0.43 #23384 review discussion and decide not follow-up 0.15 #22120 follow-up 1.15 #23340 read through discussion, think about solutions</p> <h1> 1.52 #23340 research and long-ish comment</h1> <p>4.65</p> <p>2025/07/07 Monday 0.23 github notifications 0.65 #23358 review, research</p> <h1> 0.88 #23358 comments</h1> <p>1.76</p> <p>2025/07/09 Wednesday 2.17 #23326 follow-up, work on a fix 0.10 #1674 rebase and re-push PR 23219 0.03 #1674 check CI and apply to blead 0.62 #23326 fix non-threaded, testing and re-push 1.02 #23375 review, testing and approve with comment</p> <h1> 0.45 #23370 review. research and approve</h1> <p>4.39</p> <p>2025/07/10 Thursday 2.17 #23226 testing and follow-up, work on a more extensive test, testing, push for CI/smoking 0.43 #23416 review and comment 0.88 #23419 review and comment 0.57 #23326 look into CI failures (alas Windows), fixes and</p> <h1> push</h1> <p>4.05</p> <p>2025/07/11 Friday</p> <h1> 0.13 #23226 make PR</h1> <p>0.13</p> <p>2025/07/14 Monday 0.22 #23349 review updates and approve 1.08 #23433 review and comment, work on PR for SLU to re- introduce apos in names upstream PR#141 1.18 #23226 look into openbsd test failures. debugging</p> <h1> 0.57 #23226 debugging</h1> <p>3.05</p> <p>2025/07/15 Tuesday 0.37 #23433 follow-up on SLU PR#141 1.80 #23226 debugging</p> <h1> 0.82 #23226 testing, debugging</h1> <p>2.99</p> <p>2025/07/16 Wednesday 1.80 #23226 follow-up, testing, push with a workaround, work on minor clean up, comments</p> <h1> 0.37 #23226 more follow-up, minor fix, push for testing</h1> <p>2.17</p> <p>2025/07/17 Thursday 1.28 #23429 review, comments</p> <h1> 0.13 #23413 review and approve</h1> <p>1.41</p> <p>2025/07/21 Monday 0.60 #23301 review updates and comments 0.12 #23312 followup 0.88 #23429 review, testing, research and comment 1.27 #23202 review</p> <h1> 2.02 #23202 more review, comments</h1> <p>4.89</p> <p>2025/07/22 Tuesday 0.78 check coverity scan report, reasonable errors though none apply in the circumstances reported 0.40 #23301 testing, comment 0.20 #23460 review and comment</p> <h1> 1.08 #23447 review, try to break it</h1> <p>2.46</p> <p>2025/07/23 Wednesday 0.17 #23301 review updates and approve 0.08 #23460 comment, review and approve 0.35 #23461 review upstream ticket and the change, comment 0.40 #23447 manage to break it, comment 0.28 jkeenan’s pthread thread on p5p/#23306 testing 0.40 #23462 review, comments 0.08 #23392 re-check and apply to blead 0.47 #23464 review issue, reproduce, review code, test a fix and make PR 23465 0.45 #23178 re-check and apply to blead 0.55 #23414 review, comment 0.48 #23462 look into CI failure, review some more, comment</p> <h1> 0.82 #23360 review, testing, comments</h1> <p>4.53</p> <p>2025/07/24 Thursday 1.03 #22125 rebase, testing freebsd case suggested by Dave, comment, more testing 0.20 #23468 review, research and approve 0.10 #23467 review, research and approve 0.42 #23463 research, testing and comment</p> <h1> 1.45 #23340 research, comment</h1> <p>3.20</p> <p>2025/07/28 Monday 0.30 #23481 review and comment 1.23 #23367 review, testing and approve 0.23 #23462 review updates 0.17 #23479 review and approve 1.07 #23477 review, testing 0.52 #23477 more testing, approve 0.42 #23459 review. research and comment</p> <h1> 0.58 #21877 sv_gets review</h1> <p>4.52</p> <p>2025/07/29 Tuesday 0.60 #23459 testing and comment 0.73 #23323 research and comment 0.08 #23481 review updates and approve</p> <h1> 0.32 #23488 review, research and comment</h1> <p>1.73</p> <p>2025/07/30 Wednesday 0.20 #23433 link SLU ticket #141 follow-up 0.15 #23499 follow-up 0.27 #23489 review and comment 0.18 #23491 review and approve 0.15 #23494 review and approve 0.08 #23495 review and approve 0.08 #23496 review and approve 0.08 #23498 review and approve 0.15 #23501 review, research and comment 0.38 #23503 review test results, testing without the builtin math on Linux and comment 0.47 #23508 review, try to break it and approve 0.32 #23506 review, comment</p> <h1> 1.30 #23483 review, research</h1> <p>3.81</p> <p>2025/07/31 Thursday 0.08 #23501 review and approve 0.22 #23500 review and approve 0.22 #23499 review and apply to blead 0.90 #23509 review and approve 0.33 #23514 review and approve 0.38 #23513 review and comment 1.20 #22125 try to reproduce reported freebsd failure, manage</p> <h1> to reproduce, research, more testing and comment</h1> <p>3.33</p> <p>Which I calculate is 58.25 hours.</p> <p>Approximately 60 tickets were reviewed or worked on, and 4 patcheswere applied.```</p> ]]> </content></entry><entry> <title>PEVANS Core Perl 5: Grant Report for June/July 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/pevans_core_dev_june_july_2025"/> <id>tag:news.perlfoundation.org,2025-08-06:/post/pevans_core_dev_june_july_2025</id> <published>2025-08-06T10:07:37</published> <updated>2025-08-06T10:07:37</updated> <summary> <![CDATA[ Paul writes: I didn't get any P5P work done in June, instead working on some other projects while awaiting the 5.42 release. In July I've managed to continue some work on sub signatures improvements 7 Beginnings of named parameter handling in subroutine signatures https://github.com/Perl/perl5/pull/23527 https://github.com/leonerd/perl5/tree/faster-signatures 1 Scalar-List-Utils resync with CPAN https://github.com/Perl/perl5/pull/23500 Total: 8 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>I didn't get any P5P work done in June, instead working on some otherprojects while awaiting the 5.42 release.</p> <p>In July I've managed to continue some work on sub signaturesimprovements</p> <ul><li>7 = Beginnings of named parameter handling in subroutine signatures<ul><li>https://github.com/Perl/perl5/pull/23527</li><li>https://github.com/leonerd/perl5/tree/faster-signatures (work in progress branch)</li></ul></li><li>1 = Scalar-List-Utils resync with CPAN<ul><li>https://github.com/Perl/perl5/pull/23500</li></ul></li></ul> <p>Total: 8 hours</p> ]]> </content></entry><entry> <title>Maintaining Perl 5 Core (Dave Mitchell): June 2025 </title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_dave_mitchell_june_2025"/> <id>tag:news.perlfoundation.org,2025-07-14:/post/maintaining_perl_dave_mitchell_june_2025</id> <published>2025-07-14T12:13:51</published> <updated>2025-07-14T12:13:51</updated> <summary> <![CDATA[ Dave writes: I spent last month working on rewriting and modernising perlxs.pod, Perl's reference manual for XS. It's still a work-in-progress, so nothing's been pushed yet. Summary: 49:49 modernise perlxs.pod Total: 49:49 TOTAL ]]> </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>I spent last month working on rewriting and modernising perlxs.pod,Perl's reference manual for XS.</p> <p>It's still a work-in-progress, so nothing's been pushed yet.</p> <p>Summary:* 49:49 modernise perlxs.pod</p> <p>Total:* 49:49 TOTAL (HH::MM)</p> ]]> </content></entry><entry> <title>Maintaining Perl (Tony Cook) May 2025</title> <link rel="alternate" type="text/html" href="https://news.perlfoundation.org/post/maintaining_perl_tonyc_may_2025"/> <id>tag:news.perlfoundation.org,2025-07-14:/post/maintaining_perl_tonyc_may_2025</id> <published>2025-07-14T12:11:27</published> <updated>2025-07-14T12:11:27</updated> <summary> <![CDATA[ Tony writes: 2025/05/01 Thursday 0.17 #23232 minor fixes to PR 1.32 #4106 cleanup, perldelta push for CI 1.48 #23225 more review 1.37 #23225 more review, thought I found an issue, testing, but couldn’t reproduce 4.34 2025/05/05 Monday 0.72 #23242 review, testing, nothing more to say 0.95 #23244 review, testing and approve 1.67 2025/05/06 Tuesday 0.32 #22040 testing and 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/05/01 Thursday 0.17 #23232 minor fixes to PR 1.32 #4106 cleanup, perldelta push for CI 1.48 #23225 more review 1.37 #23225 more review, thought I found an issue, testing, but</p> <h1> couldn’t reproduce</h1> <p>4.34</p> <p>2025/05/05 Monday 0.72 #23242 review, testing, nothing more to say</p> <h1> 0.95 #23244 review, testing and approve</h1> <p>1.67</p> <p>2025/05/06 Tuesday 0.32 #22040 testing and comment 0.88 github workflow discussion, win32 performance 0.45 more github workflow, email to list 0.38 #23202 read through, comment 0.98 #4106 rebase, basic testing, open PR 23262</p> <h1> 0.60 some basic Win32 profiling</h1> <p>3.61</p> <p>2025/05/07 Wednesday 0.12 #4106 fix minor issue 0.22 #23259 review, testing and comment 1.22 #23263 review and approve 0.05 #23264 review and agree (thumbs up) existing comment 0.37 #23255 review, research and approve with comment 0.32 #23234 review, consider API question and approve 0.47 #23254 review, comment 0.13 #23253 review, others have pointed out problems (subscribe to PR) 0.28 #23251 review, testing and comment 0.23 #22125 rebase, basic testing, make PR 23265</p> <h1> 2.07 #23225 more review</h1> <p>5.48</p> <p>2025/05/08 Thursday 0.22 #23254 review updates and approve 0.10 #23259 review updates and approve 1.52 #23202 review updates, comment 0.58 #22854 research 2.10 #22854 look for stuff to document here, but it seems to</p> <h1> mostly be well covered in some form or another.</h1> <p>4.52</p> <p>2025/05/12 Monday 0.42 github notifications 2.57 #22883 research, debugging, testing, long comment on #22907 0.37 #22854 minor changes, testing push and make PR 23274</p> <h1> 0.60 #23272 try to work up a fix, comment</h1> <p>3.96</p> <p>2025/05/13 Tuesday 0.33 #23225 follow-up 1.08 #23272 write some text and make PR 23276 0.25 #23275 review and comment 0.58 #23225 more review</p> <h1> 1.23 #23225 more review</h1> <p>3.47</p> <p>2025/05/14 Wednesday 0.12 #23275 comment 0.50 #23274 minor edit and follow-up 0.32 #23276 minor edit 0.08 #23279 review and approve 0.08 #23279 review and approve 1.43 #23225 more review</p> <h1> 3.18 #23037 research, testing, comments</h1> <p>5.71</p> <p>2025/05/15 Thursday 0.33 #23287 review and approve 0.68 #23282 update feature.pm and make PR 23288 (run into some github strangeness too) 1.40 #23225 more review 0.55 #23282 comment on #23288 0.40 #23261 comment</p> <h1> 1.10 #23225 more review</h1> <p>4.46</p> <p>2025/05/19 Monday 0.30 #23282 re-work docs 0.72 #23304 comment on rt.cpan ticket 0.18 #23282 more re-work docs 0.23 #23297 review and approve 0.35 #23298 review and approve 0.08 #23299 review and approve 0.25 #23301 review, checks and comment 0.08 #23302 review and approve 0.08 #23303 review and approve</p> <h1> 1.65 #23225 more review</h1> <p>3.92</p> <p>2025/05/20 Tuesday 0.48 #23301 review updates, testing and comment 0.23 #23307 testing 0.08 #23305 review and approve</p> <h1> 1.52 #23225 more review</h1> <p>2.31</p> <p>2025/05/21 Wednesday 2.92 #23225 more review, comments 1.52 #23310 debugging, fix and make PR 23312 and make issue 23313</p> <h1> 0.53 #22883 make a PR for the perlio approach, PR 23314</h1> <p>4.97</p> <p>2025/05/22 Thursday 1.48 #22883 fixes to PR, thinking and comment, on 23314, work on rebasing the 22987 PR 0.17 fix badly merged cygwin perldelta note PR 23316 1.63 #23225 final? pass over the complete changed files</p> <h1> 1.65 #23225 final? pass continued and finished</h1> <p>4.93</p> <p>Which I calculate is 53.35 hours.</p> <p>Approximately 37 tickets were reviewed or worked on.```</p> ]]> </content></entry><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> </feed>
