Luanti logo

IRC log for #luanti-dev, 2026-10-18

| Channels | #luanti-dev index | Today | | Google Search | Plaintext

All times shown according to UTC.

Time Nick Message
00:31 pgimeno_ joined #luanti-dev
01:44 YuGiOhJCJ joined #luanti-dev
02:07 YuGiOhJCJ joined #luanti-dev
04:00 MTDiscord joined #luanti-dev
06:29 MTDiscord <paradust> I added native build and game tests, using rootless podman + gVisor as the sandbox: https://lci.dustlabs.io/#/console
06:35 MTDiscord <paradust> So far 39 game failures, 23 of which are from random_mod_load_order being set in the debug build (this indicates missing dependency declarations)
08:22 Warr1024 joined #luanti-dev
08:47 Warr1024 joined #luanti-dev
10:05 MTDiscord <.zenonseth> what's your plan about this going forward -e.g include mods? because that's the kind of work I was looking into and it would be better to avoid overlap. So far as i can tell this is running commits against the games, which isn't quite my goal (I'm more interested in mods/games checking against existing engines), so just wanted to check
10:18 MTDiscord <.zenonseth> (probably should have posted this in cdb channel, moving convo there)
11:05 [MatrxMT] <y5nw> So what is the state with #17454 now? Can we merge it today or is it too late? (Note that it does not affect engine translations/Weblate)
11:05 ShadowBot https://github.com/luanti-org/luanti/issues/17454 -- Implement support for translating to English and using English as an intermediate language by varttist
11:06 Krock merging it in 10 minutes
11:06 Krock then let's enter Feature Freeze
11:08 MTDiscord <.zenonseth> driven by the Nov. 1st deadline, #17654 would be good to get in too - its more maintenance
11:08 ShadowBot https://github.com/luanti-org/luanti/issues/17654 -- Bump Android build target SDK to 36 + opt out of predictive back by ZenonSeth
11:08 Krock that can go in just fine during the feature freeze
11:09 MTDiscord <.zenonseth> ok, good
11:09 Krock as well as any hotfixes revealed during the RC test period
11:10 pgimeno joined #luanti-dev
11:14 Krock what's special about this release? code sanity fixes, lighting API, libzip dependency, texture pack priorities, emscripten improvements, listimages[], performance improvements
11:16 Krock merging ...
11:19 sfan5 you can edit non-editable textareas on android
11:26 Krock interesting. I currently do not see any path that would allow that in CGUIEditBox
11:29 Krock sfan5: would you like to have that fixed before the RC build? I wouldn't consider it a blocker
11:31 sfan5 not urgent. I'll work on a fix
11:45 Krock forum post prepared. testing the newest windows builds ...
11:45 Krock sfan5: would you please be so nice to update the /topic ?
11:45 Topic for #luanti-dev is now FEATURE FREEZE IN EFFECT. Luanti (fka Minetest) core development and maintenance. Chit-chat goes to #luanti | https://dev.luanti.org/ https://irc.luanti.org/ https://github.com/luanti-org
11:45 sfan5 like this?
11:46 Krock thanks
11:57 Krock Windows build works. Will tag and publish the release + forum post. any objections?
11:58 sfan5 sounds fine
11:59 Krock ~tell SFENCE Would you please be so nice to provide the macOS builds for 5.18.0-rc1 ? Thank you.
11:59 ShadowBot Krock: OK.
12:01 Krock done
13:49 [MatrxMT] joined #luanti-dev
13:49 hxnebula joined #luanti-dev
13:58 rubenwardy joined #luanti-dev
16:54 Panquesito7 joined #luanti-dev
17:22 [MatrxMT] joined #luanti-dev
18:23 Panquesito7_ joined #luanti-dev
18:48 MTDiscord <.zenonseth> hey for the long term prioritization of PRs, how would the devs feel about using a gh project - I haven't quite used them before but it looks like it could allow for ordering for prioritization purposes? No idea if this has been discussed before. There's a way you can add a custom project number field like say like "Votes" that only members can edit, and thus PRs can be prioritized. (this is my own repos view for issues since i don't
18:48 MTDiscord have PRs open: https://x0.at/xSck.png).
18:50 MTDiscord <.zenonseth> projects can also be private apparently just fyi
19:42 Krock the formspec priority list exists, though it's not used any more. a similar list could be added if needed.
20:15 MTDiscord <.zenonseth> the reason i'm asking its just that other than small PRs like bugfixes, I don't know what to put time into reviewing going forward, My first thought was all the one-approval PRs, but not sure
20:19 [MatrxMT] <Zughy> Oldest PRs are also a good call
20:40 MTDiscord <luatic> i would also appreciate more prioritization. i don't really care about how (labeling is also fine by me), but currently we basically only have "high priority" and "low priority" which are applied to few PRs / issues.
20:40 MTDiscord <luatic> so 90% of things just sit in this awkward inbetween space without any attached prioritization.
20:41 MTDiscord <luatic> i can try to prioritize by reactions but that's often not ideal
20:42 MTDiscord <luatic> random idea: add a label "important" or so that can be applied liberally by team members
20:43 MTDiscord <luatic> without any strings attached, just a hint for "someone (who can label things) finds this important"
20:44 MTDiscord <.zenonseth> i think the projects can also be made to count say thumbs-up reactions on open PRs (or issues prob separate project is best) - or even filter only thumbs up by the team
20:44 MTDiscord <luatic> i'm sure projects also work fine
20:45 MTDiscord <luatic> in the end it's just important that we prioritize more
21:49 Desour joined #luanti-dev
21:49 GreenXenith joined #luanti-dev
22:11 wsor4035 joined #luanti-dev
22:11 thelounge65649 joined #luanti-dev
22:12 wsor4035 joined #luanti-dev
22:21 [MatrxMT] joined #luanti-dev
22:26 mrcheese joined #luanti-dev
22:26 ZenonSeth joined #luanti-dev
22:29 panwolfram joined #luanti-dev
23:43 wsor4035 joined #luanti-dev

| Channels | #luanti-dev index | Today | | Google Search | Plaintext