Time Nick Message 15:11 sfan5 pushing in 5 minutes https://0x0.st/KMdi.txt 15:14 Krock sure 15:17 sfan5 release after that? 15:17 Krock release after that 15:20 Krock pushing to a separate branch to generate the builds for testing... 15:20 sfan5 I will check #16514 using google translate and then we can merge it too 15:20 ShadowBot https://github.com/luanti-org/luanti/issues/16514 -- Update builtin Bulgarian translation by StoyanDimitrov 15:27 sfan5 done 15:31 Krock ok. merging it. 15:31 Krock thanks for checking the translation. 15:33 Krock https://github.com/luanti-org/luanti/tree/TEMPORARY_5.14.0 15:47 Krock the windows build is OK 15:53 Krock ~tell SFENCE Would you please be so nice to provide signed macOS builds for 5.14.0? Thank you. 15:53 ShadowBot Krock: OK. 15:53 SFENCE Krock: Working on it 15:53 Krock oh you're here. it seems that tab autocomplete has failed on me 15:54 Krock sfan5: I do not have the permissions to merge https://github.com/luanti-org/docs.luanti.org/pull/279 - could you please push that button, or review? 15:56 MTDiscord i went ahead and merged it 15:57 Krock alright. thx. 15:57 Krock the forum post is done too, so from my side that's the end. Open points: Android build, and notify the package maintainers according to https://docs.luanti.org/for-engine-devs/releasing-luanti/ 15:58 Krock the usual, so to say. 15:58 MTDiscord ill open a draft pr for the website this afternoon, will have to wait till all releases are listed 15:58 Krock ah right. the link checker is not happy otherwise :3 16:00 MTDiscord could someone (maybe you Krock) make a 5.14.0 tag for the latest commit in https://github.com/luanti-org/luanti_android_deps, so I can open an issue over at f-droid about the new update 16:00 Krock sure 16:01 Krock @rollerozxa done 16:02 MTDiscord thanks 16:02 MTDiscord opened the issue at fdroid: https://gitlab.com/fdroid/fdroiddata/-/issues/3657 16:04 user2_ i'm testing 5.14.0 on arm64 and x86 linux rn 16:05 sfan5 well that's too late now ;) 16:07 Desour += 0.01 \o/ 16:16 SFENCE Do we have some a standard way how to communicate known issues to users? 16:17 SFENCE Because of #16499 16:17 ShadowBot https://github.com/luanti-org/luanti/issues/16499 -- No game sounds on macOS Tahoe 26 16:20 Krock not very standard, but logging warnings would be appropriate 16:21 Krock or if it's for compile-time, then #if + #error preprocessor directives 16:23 SFENCE macos signed builds ara avaliable in release. 16:23 Krock great. Thanks. 16:24 user2_ well, i can confirm 5.14.0 runs on arm64 + debian 12 16:24 SFENCE Something like warning text on download web site, can be enough. 16:36 sfan5 merging #16535, #16526 in 15m 16:36 ShadowBot https://github.com/luanti-org/luanti/issues/16535 -- Enable strip_color_codes by default by sfan5 16:36 ShadowBot https://github.com/luanti-org/luanti/issues/16526 -- Require 'give' priv for /pulverize and /clearinv by Wuzzy2 16:36 MTDiscord https://github.com/luanti-org/luanti-org.github.io/pull/360 website pr, pinged ruben for andriod builds 16:53 MTDiscord Why was https://github.com/luanti-org/luanti/pull/16212 closed? @luatic 16:54 MTDiscord And why does https://github.com/luanti-org/luanti/pull/16096 have Possible close?? 16:55 Krock former - idk. latter seems to have no progress 16:55 sfan5 i marked all PRs that were open for a long time and had no progress with 'possible close' a while ago 16:56 Krock closing PRs due to inactivity seems harsh at first, but if changes are needed and no progress is made in a while, then it's often easier to close them until they're picked up again 16:56 sfan5 not much point keeping drafts open 16:57 sfan5 if you want a commitment that the team supports a feature then that'd be an issue 16:57 Krock such that the Pull request list mostly contains PRs that can be reviewed, or reviewed soon. 16:57 [MatrxMT] We also need #16468 16:57 ShadowBot https://github.com/luanti-org/luanti/issues/16468 -- Update roadmap by Zughy 16:57 cheapie re: #16526 - is the idea for MTG to then override these back to being priv-less (since that makes sense in that game) or should I be prepared to do so in a separate mod? 16:57 ShadowBot https://github.com/luanti-org/luanti/issues/16526 -- Require 'give' priv for /pulverize and /clearinv by Wuzzy2 16:58 [MatrxMT] I'm not at home currently, so feel free to adjust the wording 16:58 sfan5 cheapie: feel free to propose that in MTG 16:58 Krock cheapie: I think MTG should customize that 16:58 Krock however, do require "interact" at least. 16:59 cheapie interact is fair 17:01 MTDiscord Its not even worth giving people anything to look forward to in blog posts at this point, nothing useful ever gets finished :/ 17:01 MTDiscord (this is an exaggeration, useful things get merged all the time, just seldom ground-breaking or relevant to many) 17:03 Krock yes, we've had more spectacular releases in the past 17:03 sfan5 I think the draft PRs likely to be featured in a blog post are likely to be exactly those that need much work (and thus might fall stale in the meantime) 17:03 MTDiscord Is there any quantifiable reason many of these PRs are stagnating? 17:03 Krock and those were longer in development. currently we're at 3 months, and nothing much happened. 17:04 MTDiscord The 3 month cycle isnt really relevant when these PRs are stale for that long anyway 17:05 cheapie sfan5: https://github.com/luanti-org/minetest_game/issues/3214 should work, if the idea gets rejected I'll just throw together a quick mod for it 17:06 sfan5 I usually only open a PR when something is finished and mergeable, so my PRs would probably never make it into the blog posts "upcoming features" section 17:06 sfan5 (I assume) 17:07 MTDiscord That isnt a fair comparison; You are a dev, you automatically have one approval and are almost guaranteed to have your additions merged. Others have to open a PR to determine if their work is even acceptable. 17:08 MTDiscord The matrix, scene color, and morph animation PRs were dead before 5.13.0, FWIW. 17:09 sfan5 I'm not complaining that the blog posts are being unfair towards my contributions, just saying that there's probably an unfortunate bias 17:10 MTDiscord I couldnt put your PRs in the "looking forward to" section even if I wanted to-- if you dont open them until they are ready to be merged, obviously there is nothing to look forward to 17:10 sfan5 yes that's what I mean 17:11 MTDiscord Its not really a bias if I have no other options 17:12 MTDiscord seems like the discussion is getting side tracked from greenxeniths orginal point 17:12 sfan5 as an exception I did open #15968 and it will surely be finished within 3 months 17:12 ShadowBot https://github.com/luanti-org/luanti/issues/15968 -- Array textures proof-of-concept by sfan5 17:12 sfan5 either way I think it's good if the looking-forward section is contexualized more as "some people are playing around with XYZ feature and it might get into the engine at some point". so that nobody is disappointed. 17:13 MTDiscord Sure, I agree, but wsor is correct; The blog section is a symptom. I want to know why every single thing I put in there (pretty much, for the last few blog cycles) has stagnated 17:14 sfan5 development is hard 17:14 MTDiscord i think you know green, its the age old problem of open a pr it may get merged in 4 years, or killed 17:15 MTDiscord Thank you for a new motivator to fix that 18:04 user2_ 5.14.0 runs on my old x86 machine (not x86_64) with debian 12 18:07 Desour there was a meeting scheduled for now btw 18:18 Krock the meeting point would be the release. the release is still ongoing. so I don't see much need for a meeting. 18:20 MTDiscord (I will have the blog post PR up within the hour) 18:54 MTDiscord Weird that it is now better to manually generate images and dynamic_add_media with caching disabled than using texture modifiers for repeatedly-generated textures 18:55 MTDiscord I'm actually not clear on what ephemeral is even for now 18:56 MTDiscord Hm, I guess it is more about server caching 19:48 MTDiscord https://github.com/luanti-org/blog/pull/171 20:10 luatic greenxenith: i'll try to get back to picking up those PRs again as soon as i'm done with my bachelor thesis, so in about 3 weeks (my thesis deadline is sooner, but i also have to give a presentation a bit later) 20:14 MTDiscord This is known, which is why it confuses me that the PRs were closed. They aren't dead, just on hold. 22:15 MTDiscord Blog post PR has media/cover image now. A quick glance from pretty much anyone would be appreciated 23:01 MTDiscord Cool build in cover image 23:07 [MatrxMT] Just came home, #16468 still open with the new release out and the milestone closed. What the fuck? 23:07 ShadowBot https://github.com/luanti-org/luanti/issues/16468 -- Update roadmap by Zughy