2023-11-29 UTC
omz13, barnaby, GWG, trwnh, yyolk, milkii_, Guest9641, IWDiscord, [0x3b0b], [snarfed], gRegorLove_ and [fluffy] joined the channel
# 10:55 sknebel angelo: do you want someone else to merge your mf2py PRs? because a bunch are ready to go but not merged yet Guest6, gRegorLove_ and gRegorLove__ joined the channel
# 15:24 Loqi sknebel has 2 karma in this channel over the last year (33 in all channels) # 15:25 sknebel (had a back-and-forth at work about that earlier and thought "wait, we didnt talk about that for mf2py either" :D (question if the reviewer merges or the author)) # 15:27 sknebel in open-source its kinda common because the common case is that the PR author can not merge # 15:28 [snarfed] yeah I guess only unusual when the submitter is a committer [schmarty] joined the channel
# 16:54 [tantek] or they are in vastly different timezones so waiting for the committer to merge after the reviewer has approved the review may mean an 8-16 hour delay kpawlx and [jacky] joined the channel
# 18:24 Loqi auto-merge-because-theres-way-too-many-tests has 1 karma over the last year # 18:51 [snarfed] [capjamesg] angelo sknebel, do you all know who's leading the mf2py 2.0 release? IWSlackGateway, [Paul_Robert_Ll], [jacky] and [tantek] joined the channel
# 19:48 capjamesg I don't have the bandwidth to review individual PRs right now. # 19:56 [snarfed] oh not reviewing PRs, I was thinking more of the release lead [aciccarello] and [marksuth] joined the channel
# 22:22 angelo i need to add docstring/changelog/documentation to the various PRs # 22:23 angelo i wasn't sure who should merge. i'll merge after i do that. # 22:23 Loqi angelo has 4 karma in this channel over the last year (7 in all channels) # 23:57 capjamesg Can we review / merge all currently open PRs and then do a 2.0 release? # 23:58 capjamesg This feels like a good point to work through the backlog, then do a strong release. # 23:59 Loqi capjamesg has 8 karma in this channel over the last year (121 in all channels)
