Maintaining Perl (Tony Cook) February 2025
Fri, 09-May-2025 by
alh
edit post
<![CDATA[
Tony writes:
```
[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
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 review and comments
1.23 #22967 review, comments
=====
3.18
2025/02/05 Wednesday
2.02 #22959 debuggging, work up a fix and push for CI
1.25 #22423 debugging, work on tests
=====
3.27
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
1.00 #22423 debugging tied hash case
=====
3.76
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
1.80 #22423 try to work up a fix for tied hash cases
=====
4.78
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 $_),
which is a known RE problem.
=====
2.33
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
2.38 #22752 more rebase
=====
4.08
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
1.20 #22884 testing and comment
=====
4.90
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
0.48 #22423 fix CI error, push for CI
=====
2.77
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
0.63 perldelta for switch re-work, make PR 23013
=====
4.77
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
0.40 #23013 minor change and apply to blead
=====
3.77
2025/02/24 Monday
2.20 #23019 research and comments
0.77 #23022 work on reproduce and reproduce, comment
2.27 #23022 debugging, work on a fix, push for CI
=====
5.24
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
0.23 #23022 look into CI failure and fix
=====
3.44
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
0.80 #21877 approach from the other direction (sv_gets)
=====
4.11
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
0.52 clangsa: review more reports
=====
2.66
2025/02/28 Friday
0.37 #23037 comment
=====
0.37
Which I calculate is 56.41 hours.
Approximately 39 tickets were reviewed or worked on, and 2 patches
were applied.
```
]]>
Comments (0)
