Time  Nick           Message
13:45 [MatrxMT]      <Zughy> Uhm, considering all the SDL switching in the works, should we have a 3-4 week long feature freeze instead of 2?
13:47 sfan5          why? more bugs?
13:47 sfan5          merging #15554, #15531, #15525 in a variable amount of time > 10m
13:47 ShadowBot      https://github.com/minetest/minetest/issues/15554 -- Reorder client initialization (rebased) by SmallJoker
13:47 ShadowBot      https://github.com/minetest/minetest/issues/15531 -- [no squash] Group sparse mesh buffers over entire scene for rendering by sfan5
13:47 ShadowBot      https://github.com/minetest/minetest/issues/15525 -- Add glTF STEP interpolation support by appgurueu
13:53 [MatrxMT]      <Zughy> sfan5: it feels like it won't be easy to get rid of all the issues we currently have (scancodes, opengl3 and the like)
13:54 sfan5          the freeze will be as long as we need to fix everything anyway. so I don't see the need to prematurely extend it
13:59 [MatrxMT]      <Zughy> Uhm, I thought we were sticking to fixed dates..
14:19 sfan5          best-effort yes
14:22 sfan5          I don't remember exactly what we discussed, but I think the idea was to not delay release dates to wait for feature PRs
19:32 [MatrxMT]      <y5nw> Zughy: for my SDL PRs it would IMO make more sense to give more time to test these. That is not directly related to a long feature freeze period
19:34 MTDiscord      <herowl> If people aren't testing them now, the only way to get more people testing is merging into master.
19:50 [MatrxMT]      <y5nw> Well the scancode PR has seen some testing and code review so it doesn't matter much (to me) whether it is merged sooner or later. Simply extending the feature freeze would not work - even the apparent/perceived "worst case" of disabling SDL again (if needed: we add the scancode PR to the switching) is IMO better than that because rushing a solution/fix (especially for something like keyboard input, where people have different/uncommon
21:56 MTDiscord      <luatic> your message got cut off after "different/uncommon" (configurations?)
22:05 [MatrxMT]      <Zughy> "different/uncommon setups) does not work if we find a regression and we would then end up extending the feature freeze like we did for 5.9.0 (and did the extended feature freeze lead to the keyboard regressions being addressed? no)"
22:21 chmodsayshello is a f1000 in minetest's code actually 1000 bits/125 bytes big in memory?
22:24 MTDiscord      <luatic> no, iirc it's just floats but even worse, sends something like a truncated float / 1000 or something iirc
22:25 chmodsayshello alright, thanks