Maintaining Perl (Tony Cook) March 2025
Fri, 09-May-2025 by
alh
edit post
<![CDATA[
Tony writes:
```
[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
0.78 #23044 research and comment
=====
3.39
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
0.25 #23041 review
=====
3.71
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
0.27 #22423 write a perldelta and push, make PR 23073
=====
4.03
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
1.22 #16608 research
=====
4.46
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
0.93 unicode discussion #p5p and testing
=====
4.10
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
1.52 #23037 review discussion, research and comment
=====
2.33
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
0.32 #23093 review, check C::J::XS and approve
=====
3.56
2025/03/13 Thursday
0.37 #23091 review and approve
1.98 #23096 review...
0.65 #23096 review and approve
0.47 #23037 #p5p discussion
=====
3.47
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
0.57 #23114 research and comment
=====
3.47
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
D::PPP, testing, push for CI
=====
3.22
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
0.68 more dist-modules, try to work what introduced 5.8 failure
=====
3.34
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
review
=====
3.13
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
0.98 #23151 try to work up a testable case
=====
3.93
2025/03/25 Tuesday
1.68 #23151 more work on a testable case
0.97 #23081 research, code profiling and approve with comment
0.85 #23108 testing and comment
=====
3.50
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
0.58 #23156 review and comments
=====
3.20
2025/03/27 Thursday
2.35 #23075 check ppport.h CI results, rewrite since the API
changed, testing and push for CI again
1.13 #23075 test cleanup, testing
=====
3.48
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
CI
=====
4.57
Which I calculate is 60.89 hours.
Approximately 60 tickets were reviewed or worked on, and 2 patches
were applied.
```
]]>
Comments (2)
That sounds like an incredibly ambitious and visionary project you've undertaken! The idea of such revolutionary advancements in AI and quantum crypto is certainly captivating. We wish you the best in finding the trusted collaborators you need to bring your innovation to light. -
https://www.thegoodpoolcompany.com
