| Time |
Nick |
Message |
| 01:21 |
|
mrcheese joined #luanti-dev |
| 05:00 |
|
MTDiscord joined #luanti-dev |
| 09:16 |
|
nekobit joined #luanti-dev |
| 09:22 |
|
Warr1024 joined #luanti-dev |
| 09:45 |
Krock |
pushing https://pastebin.com/raw/vadVZfdf in 20min unless someone complains (see #luanti discussion 12 hours ago) |
| 09:47 |
|
Warr1024 joined #luanti-dev |
| 12:05 |
sfan5 |
glad people are actually using the dev builds, or we would only figure out after release |
| 12:17 |
|
mrcheese joined #luanti-dev |
| 12:38 |
Krock |
hmm an RC build might be due soon |
| 12:47 |
|
Desour joined #luanti-dev |
| 13:51 |
sfan5 |
merging #16781, #16804 soon |
| 13:51 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16781 -- Allow sneak toggling when player does not have the fly privilege by y5nw |
| 13:51 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16804 -- Raise MAX_REGISTERED_CONTENT by sfan5 |
| 15:46 |
sfan5 |
when's the meeting today? |
| 15:58 |
MTDiscord |
<wsor4035> while https://github.com/luanti-org/luanti/issues/6101 was closed, yay, higher limit now, unless the underlying issues such as allowing nodes to have multiple textures, meshes, etc sort of stuff is added, someone is just going to essentially remake that issues as Allow registering more than ~58k nodes. so my question is as a triager, if someone does make that issue, should we instead figure out which thing they actually want and get |
| 15:58 |
MTDiscord |
that as an issue instead of just forever having raise the node limit issues? |
| 15:59 |
sfan5 |
yes |
| 16:00 |
MTDiscord |
<wsor4035> any objection to me putting a comment to that effect in the (closed) issue for people looking up node limit in the future? |
| 16:01 |
sfan5 |
go ahead |
| 16:01 |
MTDiscord |
<wsor4035> thanks |
| 16:08 |
Krock |
18:00 UTC, which is in 2 hours. |
| 16:30 |
|
Desour joined #luanti-dev |
| 16:52 |
sfan5 |
anyone want to have a look at game#3211? |
| 16:52 |
ShadowBot |
https://github.com/luanti-org/minetest_game/issues/3211 -- Translation of the game description by alrito28 |
| 18:01 |
sfan5 |
meeting time, @Zughy, Krock, @luatic |
| 18:01 |
sfan5 |
also pinging rubenwardy, Desour in case they're here |
| 18:01 |
rubenwardy |
Hello |
| 18:01 |
Desour |
o/ |
| 18:01 |
Krock |
greetings |
| 18:02 |
sfan5 |
meeting notes https://docs.luanti.org/for-engine-devs/meetings/#2026-01-04 |
| 18:02 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/2026 -- Fix endian.h include for FreeBSD by AMDmi3 |
| 18:02 |
Krock |
> Feature freeze and release 18 January to avoid stress to whom goes to FOSDEM (Zughy) |
| 18:03 |
Krock |
Milestone: https://github.com/luanti-org/luanti/milestone/31 |
| 18:03 |
sfan5 |
i am in favor, we have more than enough in the release and let's not delay stuff. |
| 18:03 |
MTDiscord |
<sfence> Hello |
| 18:04 |
Krock |
160 commits as of currently. A few more will come as we update the translations |
| 18:05 |
Krock |
to release on 18th we'd essentially need to enter feature freeze now |
| 18:05 |
Krock |
such that an RC build can be tested for two weeks |
| 18:05 |
MTDiscord |
<wsor4035> regarding that, is https://github.com/luanti-org/luanti/pull/16808#issuecomment-3708287730 + depending on pr wanted before 5.15 feature freeze? |
| 18:06 |
sfan5 |
PR prioritizing is a seperate meeting point |
| 18:06 |
Krock |
I don't care about the release cycle, so either is fine by me. |
| 18:07 |
MTDiscord |
<luatic> I'm fine with starting feature freeze |
| 18:07 |
Krock |
any other opinions? |
| 18:08 |
Krock |
If not - then just go ahead like that. Translation update in the next few days + RC build |
| 18:09 |
sfan5 |
ok then let's do that |
| 18:09 |
sfan5 |
i'll do the translation updates later and whoever has time and motivation can release an rc build |
| 18:09 |
sfan5 |
next: > decide which feature PRs to still get into 5.15.0 (if any) |
| 18:09 |
Krock |
I'll have a look at the RC build, afterwards the changelog |
| 18:10 |
sfan5 |
thx |
| 18:10 |
Krock |
that means low-hanging fruits would still be possible to get in |
| 18:10 |
sfan5 |
i think we should remove #15992, #16608 from the milestone since we're freezing now |
| 18:10 |
ShadowBot |
sfan5: Error: That URL raised <Connection timed out.> |
| 18:10 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16608 -- Add meta item image override functions by cx384 |
| 18:10 |
Krock |
yes. move to 5.16.0 |
| 18:10 |
sfan5 |
(15992 = Make ABMs changeable) |
| 18:11 |
sfan5 |
#16787 is a low-hanging fruit IMO |
| 18:11 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16787 -- Add new setting to enable/disable dark mode in main menu by sfan5 |
| 18:11 |
sfan5 |
#16808 as mentioned by wsor might make sense too |
| 18:11 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16808 -- Add PlayStation 5 DualSense controller support by thierry-f-78 |
| 18:11 |
sfan5 |
possibly #16798 too |
| 18:11 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16798 -- Outline focused element when tab is pressed. by siliconsniffer |
| 18:12 |
Krock |
I'd suggest to get the controller PR merged - although I cannot test it, thus code review only. and that part looks good. |
| 18:12 |
[MatrxMT] |
<y5nw> Can we also add #16803? It is largely ready at this point |
| 18:12 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16803 -- Implement secondary keybindings [UI Proposal 2] by y5nw |
| 18:13 |
sfan5 |
sounds okay too |
| 18:16 |
Krock |
the keybindings layout does fit surprisingly well into the settings menu. seems useful. |
| 18:16 |
sfan5 |
more opinions? (rubenwardy, Desour?) |
| 18:17 |
Desour |
didn't look at it so far, tbh |
| 18:17 |
Krock |
the "problem" with that PR is that we'd have to delay the translation update, or do it multiple times |
| 18:18 |
sfan5 |
we could merge it today then |
| 18:18 |
sfan5 |
assuming it works |
| 18:18 |
Krock |
otherwise we'd lack a few strings, which wouldn't be too bad either. |
| 18:18 |
Krock |
I'll give it a try quickly. If there's issues then the RC testers hopefully will find it |
| 18:25 |
sfan5 |
sooo anything else? |
| 18:29 |
|
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 |
| 18:29 |
Krock |
afaik no |
| 18:30 |
[MatrxMT] |
<Zughy> I'm interested in knowing #16806 's fate |
| 18:30 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16806 -- Run place/secondary_use functions also when dig is held down by Zughy |
| 18:33 |
MTDiscord |
<landarvargan> Exposable to games/mods too? |
| 18:33 |
MTDiscord |
<landarvargan> (in reply to dark mode option) |
| 18:33 |
MTDiscord |
<wsor4035> its in the main menu, why would it need to be something other than a client setting? |
| 18:34 |
sfan5 |
i think the idea is to default to dark mode depending on game.conf? |
| 18:34 |
MTDiscord |
<wsor4035> ah |
| 18:35 |
sfan5 |
but let's not. this is intended for user choice |
| 18:35 |
MTDiscord |
<landarvargan> I guess I should say servers |
| 18:35 |
MTDiscord |
<landarvargan> Probably best for another issue though |
| 18:37 |
sfan5 |
🤔 |
| 21:09 |
pgimeno |
what happened to the rule of merging a PR with just 1 CD approval including the author, if there's basically no risk of breaking anything? Has it been taken back, or is it now permanent? |
| 21:10 |
sfan5 |
permanent |
| 21:11 |
pgimeno |
ah nice, thanks |
| 23:32 |
|
panwolfram joined #luanti-dev |
