Maintaining Perl (Tony Cook) June 2026
Sat, 18-Jul-2026 by
alh
edit post
<![CDATA[
Tony writes:
```
[Hours] [Activity]
2026/06/01 Monday
3.15 security list #148
1.67 security list #148
=====
4.82
2026/06/02 Tuesday
0.87 atomic stuff on list
0.62 #24447 review discussion, ci results and comment
0.20 #24440 review
0.48 #24440 more review, simple testing and comment
1.17 #24451 review and comment
=====
3.34
2026/06/03 Wednesday
0.27 #24451 review updates
=====
0.27
2026/06/04 Thursday
1.05 #24451 more review, comments
0.15 #24304 comment
1.82 #24439 review, work on a fix for an issue this exposed,
push for CI
1.38 #24439 review
=====
4.40
2026/06/05 Friday
0.77 #24453 research and comment
1.35 #24439 more review
1.23 #24439 more review
=====
3.35
2026/06/08 Monday
1.33 #24451 review updates, testing and comments
1.18 #24439 more review, look into only apparently relevant
smoke-me failure and can’t reproduce, comment
0.15 #24454 review and approve
0.23 #24455 review, research and approve
0.50 #24459 review
1.18 #24459 more review, comments
0.50 #24418 debugging
=====
5.07
2026/06/09 Tuesday
0.43 #24451 av_splice - tied SPLICE returns more elements -
testing and comment
1.27 #24463 review, testing and approve
0.77 #24448 review, testing
0.97 #24448 more review, testing, comments
1.02 #24418 debugging
=====
4.46
2026/06/10 Wednesday
0.52 #24447 review updates and comment
2.52 #24418 debugging, work on a fix, test cases, testing, push
for CI
0.30 #24418 perldelta
=====
3.34
2026/06/11 Thursday
0.20 #24465 review and approve
1.40 :utf8 strict
1.02 :utf8 strict
=====
2.62
2026/06/12 Friday
2.13 Pauls AV API, emails
=====
2.13
2026/06/15 Monday
2.02 #24471 review, testing, research and comment
1.30 #24472 review OP and downstream patch, try to reproduce a
similar configuration on FreeBSD and succeed(ish - it
failed to build)
1.08 #24472 try to work up a fix
=====
4.40
2026/06/16 Tuesday
0.20 #24475 review, compare old workflow reports against PR
workflow run, approve
0.17 #24476 review, check old and PR workflow runs, approve
0.30 #24477 review, check old and PR workflow runs, comment and
approve
0.65 #24474 review, research and approve
0.37 #24473 review and comment
0.63 #24472 Configure detection of quadmath fpclassify
1.13 #24472 more Configure, work on the actual code
=====
3.45
2026/06/17 Wednesday
0.25 #24473 review and approve
0.92 #24478 review and comment
1.75 #24459 review, testing and comments
1.15 #24472 re-work Configure a bit, work on failing POSIX
build on freebsd, testing
=====
4.07
2026/06/18 Thursday
0.45 #24471 review updates and discussion
1.77 #24459 review discussion, research and comment, check for
a possible TARG leak and it’s not an issue.
0.12 #24482 check CI results and restart (failed due to
infrastructure)
0.40 #24483 comment (after looking back at the relevant IRC
discussion, no ticket?)
0.13 #24485 comment
0.68 #24484 review and comments
1.73 #24472 try to fix failures (one is
../lib/ExtUtils/t/Embed.t)
=====
5.28
2026/06/22 Monday
0.83 #24484 review updates and approve
0.12 #24483 review update and approve
0.43 #8309 research and follow-up
0.08 #24478 review updates and approve
0.32 #24447 review updates, start CI and check for build
warnings, approve
0.38 #24105 review update and research
0.08 #24459 follow-up
1.27 #24472 debug build issue
0.72 #24472 more debug build issue
=====
4.23
2026/06/23 Tuesday
0.92 #24497 review
1.40 5.44 RC testing - win x86_32, freebsd x86_64, macos arm,
cygwin, win x86_64
1.00 fix macos readdir_r warning - reproduce, fix, testing,
push for CI
0.47 fix macos is_codeset_name_UTF8 warning, explore a sea of
macro definitions
=====
3.79
2026/06/24 Wednesday
0.47 fix macos is_codeset_name_UTF8, more macro decoding, make
PR for readdir_r change
1.65 #24495 review, research and comments
0.58 #24489 review and comments
0.57 #24493 review, research and comment
0.22 macos uselongdouble noise, arm64 doesn’t really have ldbl
0.83 win32 run/todo.t noise - better way to get DEBUGGING?
=====
4.32
2026/06/25 Thursday
1.20 #24472 build a quadmath win32 perl, research
1.82 #24472 beat head against the mingw build wall, testing,
more research and comment
=====
3.02
2026/06/26 Friday
1.47 #24502 review, testing
=====
1.47
2026/06/29 Monday
0.68 #24447 follow-up
0.12 #24504 review
0.40 #24503 review
1.42 #24502 more review and testing, comment
0.67 #24513 review, research and comments
0.12 #24505 review and approve
1.20 #24508 review, comments
=====
4.61
2026/06/30 Tuesday
0.33 #24508 follow-up
0.13 #24513 review updates and comment
1.03 #23918 comment in associate Algorithm::Heapify::XS ticket
and open a related Algorithm::Heapify::XS ticket
0.92 #24502 more review, comment
0.70 #24518 review and comment with test code
1.12 #23918 look at adding sv_numcmp etc to ppport
=====
4.23
Which I calculate is 76.67 hours.
Approximately 40 tickets were reviewed or worked on.
```
]]>
Comments (3)
This article was both informative and enjoyable to read. I like how the topic was broken down into manageable sections, making it easier to understand. It's always nice to find content that teaches something valuable while remaining engaging and approachable. credit repair bradenton
This was a valuable read for anyone interested in open-source software and the long-term maintenance of programming languages. Keeping mature projects healthy requires a lot of dedication behind the scenes, so it’s great to see that work being discussed and recognized. credit repair auburn hills
It's essential to keep this momentum going, especially with the diverse range of issues you've addressed. The combination of reviews, testing, and research reflects a thorough understanding of the projects at hand. If you’re looking for ways to streamline your process or perhaps tackle some of the more complex issues, consider collaborating with colleagues who might have insights or experience that could benefit your current workload.
tela g..., Hills solar companies
