Maintaining Perl (Tony Cook) July 2024
Wed, 14-Aug-2024 by
alh
edit post
<![CDATA[
Tony writes:
```
[Hours] [Activity]
2024/07/01 Monday
0.42 #22333 review and approve
0.08 #22349 review update and approve
0.08 #22323 review update and approve
0.08 #22341 review update and approve
0.10 #22324 review update and approve
0.07 #22344 review update and approve
0.12 #22355 review and approve
0.37 #22356 review, research and approve
0.13 #22357 review, research, comment and approve
0.10 #22358 review and approve
0.08 #22359 review and approve
1.42 #22362 review, testing, debugging, research and comment
0.83 smartmatch removal: more testing, push for CI/smoke
1.27 review coverity scan results
=====
5.15
2024/07/02 Tuesday
0.23 github notifications
0.22 smartmatch removal: check CI/smoke results
0.18 #22362 review updates and approve
0.08 #22363 review and approve
0.37 #22369 review and approve
0.38 #22364 review, testing and approve
0.28 #22366 review and comment
1.32 #22255 work up a fix, a test, testing, push for CI
0.63 #22169 improve tests, testing
=====
3.69
2024/07/03 Wednesday
0.15 #22255 re-check, minor adjustments, testing, make PR 22371
2.63 #22329 re-work gv_fetchmeth_() docs as suggested, look
into GV_NOUNIVERSAL history
1.37 #22169 fix mis-undefinition of “new”, testing, polish,
push for CI
0.12 #22255 bump $XS::APItest::VERSION
0.17 #22308 check if fixed via smoke logs and close
=====
4.44
2024/07/04 Thursday
0.08 github notifications
0.57 #22255 apply to blead, perldelta, porting fix
0.32 #22076 apply to blead, don’t think it needs perldelta
0.28 #22366 review and approve
0.32 #22367 review, research history of the code, approve
0.20 #22368 review and approve
0.15 #22373 review discussion, comment
2.67 #799 work on a fix, testing, regression test, push for CI
=====
4.59
2024/07/08 Monday
0.98 #22169 remove DOES TODO, rearrange the code, testing
0.87 #799 fixes for issues from mauke, other fixes
0.52 #799 more polish, testing, force push and comment
0.25 #22329 follow-up comment
0.18 #1200 review and mark closable
0.08 #1420 track back to PR #19125
0.67 #1496 review discussion, research and close
0.22 #1500 review discussion
0.12 #1509 review discussion
0.07 #1674 review discussion
0.13 #1718 review discussion
=====
4.09
2024/07/09 Tuesday
1.42 #799 re-work, testing, comment
0.87 #22380 review test failure, review UUID::FFI code, comment
0.45 #22380 research, comment
0.40 #22329 review update and approve
2.02 re-work dist modules CI, make test-dist-modules safer by
default, try to get threads, win32 tests
=====
5.16
2024/07/10 Wednesday
0.47 re-work dist modules CI: look into test failures, re-work
the CI labels, push for another CI run
0.27 #799 minor cleanup, re-push
2.57 re-work dist modules CI: fixes, fixes
1.52 re-work dist modules CI: fixes, Storable, try to get some
debugging info
=====
4.83
2024/07/11 Thursday
0.45 #22331 build to review docs, and approve
0.77 re-work dist modules CI: remove windows support for now,
commit cleanup/rebase/squash, polish, testing, push for CI
1.13 Win32.pm PR #39 import, testing, push for CI
0.08 re-work dist modules CI: check CI results and make PR
#22392
0.08 Win32.pm PR #39 import, check CI results and make PR
#22393
0.10 #22384 review and comment
0.18 #22242 review, review discussion and approve
0.35 #22243 review, approve and comment
0.15 #22387 review, apply to blead, perldelta
0.10 #22388 review and apply to blead (no perldelta needed)
0.12 #22391 review and comment
0.53 #22380 consider change, comments, try the change and tests
fail, review perlpacktut, I don’t think making it always
SvPV_force() is reasonable.
1.00 #22385 review code, build to debug, debugging and comment
=====
5.04
2024/07/12 Friday
0.23 any/all email thread
=====
0.23
2024/07/15 Monday
0.57 #22385 research, follow-up comment
1.65 #22380 research, comment, work on a fix, push for CI
0.20 #22380 fix an issue found by CI, force push
1.55 #22393 work on CI update to test on 32-bit win32, testing
0.33 #22405 review, try a test, comments
0.92 #22393 local testing, research: can we do github CI
unprivileged? (apparently not), comment
=====
5.22
2024/07/16 Tuesday
0.92 #22392 updates, add some documentation, testing, rebase,
force push
0.37 #799 look at b postpone subname
2.43 #799 more look at b postpone subname (which appears to
have been broken for a long, long time), fix it, testing,
push for CI
=====
3.72
2024/07/17 Wednesday
0.18 #22392 review discussion, apply to blead, doesn’t seem to
need a perldelta (has no effect on end users)
0.18 #22403 review and approve
0.18 #22273 review and approve
0.37 #22393 apply to blead and perldelta
1.30 #22232 work on fixes, testing
0.15 #22232 push fixes, comments
0.30 #22386 review, research and approve with comment
1.40 #22370 split up commit
=====
4.06
2024/07/18 Thursday
0.08 github notifications
0.08 ppc #50 review
0.58 #22373 review, research, comment
0.17 #22411 review, comment on CI failure
1.18 #22370 more split up commit
1.02 #22370 more split up commit, testing, push to update PR
=====
3.11
2024/07/22 Monday
0.45 #22415 review discussion, research and comment
1.90 #22370 fix issues from PR reviews
0.42 #22415 research and follow-up comment
1.53 #22377 partly review up to 885566
0.92 #22394 work on a fix, push for CI
=====
5.22
2024/07/23 Tuesday
0.10 #22394 check CI results, check messages, minor test nit
fix, testing, push and make PR 22420
0.17 #799 apply to blead, perldelta
0.23 #22419 review and approve
0.55 #22418 review, research and briefly comment
0.17 #22421 review, comment on a typo
0.38 ppc #51 review
0.48 #21877 look into my remaining concern on this (possible SV
leak?)
0.12 #21877 too much noise with DEBUG_LEAKING_SCALARS :/
0.20 #22394 fix per review, testing, force push
0.18 #22370 check rebase
0.25 #22232 apply to blead, perldelta
1.47 #21877 look into different approaches (stap is unfriendly)
=====
4.30
2024/07/24 Wednesday
0.28 github notifications
0.75 #22421 review and approve
0.08 #22303 comment
1.53 #22423 debugging, briefly comment
0.53 #22422 review and approve
0.55 #22414 review, review discussion and comment
0.70 #22400 review, testing, comment
0.55 #22377 more review up to d81a28db
=====
4.97
2024/07/25 Thursday
2.60 #22377 more review and finally approve
2.53 #1420 work on last part of fix
=====
5.13
2024/07/29 Monday
0.25 #22427 review and approve
0.30 #22428 review, comment and approve
0.17 #22432 review and approve
0.13 #22433 review, review discussion and close
0.23 #22434 review and approve
0.15 #22435 review and approve
0.08 #22437 review and approve
0.28 #22420 apply to blead, perldelta
0.55 #22303 fix some issues
0.93 #22303 more fixing, testing
1.03 #1420 more work on last part of fix, look for a test case
=====
4.10
2024/07/30 Tuesday
0.70 #22415 review discussion and comment
0.70 #22442 testing and comment
0.35 #22443 review and comment
0.37 #22425 testing, research and comment
0.43 #1420 more fixing, testing, debugging
2.30 #1420/#19124 finish(?) fixes, testing
=====
4.85
2024/07/31 Wednesday
0.25 #22444 review, review discussion and comments
0.35 #22443 review updates and approve
0.33 #22442 review discussion, testing
1.35 #22450 review and comments
0.45 #22445 review, comments
1.63 #1420/#19124 commit messages, code re-check
=====
4.36
Which I calculate is 86.26 hours.
Approximately 79 tickets were reviewed or worked on, and 9 patches
were applied.
```
]]>
Comments (0)
