Time Nick Message 07:09 MTDiscord How does the core dev team about a very gradual replacement of irr_pointer with std::unique_ptr and std::shared_ptr, variable by variable. Working from the minetest/minetest project until minetest/irrlicht can be worked on? 08:05 sfan5 irr_ptr is for interacting with irrlicht's IReferenceCounted, I don't think a gradual replacement is possible. you'd need to touch everything at once (esp. the gui code) 08:31 MTDiscord Yeah, I'm trying my best 12:13 MTDiscord <.niklp> sorry for asking again, but it would be very nice if the mtg repo could get a 5.8.0 tag (and shouldn't cdb get a mtg update too?) 12:15 ROllerozxa yes, I'm unsure why this hasn't been done. I could make a new release for MTG on CDB myself but I'd want to wait until a tag has been made 17:22 [MTMatrix] https://udongein.xyz/notice/Acbed3a61m4ijt2Bns 17:29 MTDiscord <.niklp> 5.8.0 is newer than 5.8.0-dev https://github.com/minetest/minetest/#version-scheme 17:34 [MTMatrix] oopse... 19:54 grorp Merging #14055, #14057, #14067 in 15 min 19:54 ShadowBot https://github.com/minetest/minetest/issues/14055 -- Improve Irrlicht instructions by garymm 19:54 ShadowBot https://github.com/minetest/minetest/issues/14057 -- Check if liquid can flow into empty node before picking it as source by ZenonSeth 19:54 ShadowBot https://github.com/minetest/minetest/issues/14067 -- Fix Devtest "get_version" unittest failure on release versions by grorp 20:31 MTDiscord Can we has the async lua mapgen environment? 20:44 MTDiscord Also can we has https://github.com/minetest/minetest/pull/13987 20:54 sfan5 async mapgen is not ready 20:54 sfan5 missing a genericaziation of gennotify 20:55 sfan5 maybe I have time to work on it next week 20:55 MTDiscord sfan5 what's the plan going forward for MTG releases? rolling? should we create a 5.8 release? 21:00 sfan5 5.8 yes 21:00 sfan5 in the future rolling sounds ok to me but some Q: what will be the version number? won't mtg have to be come more compatible with diff. engine versions? 21:02 MTDiscord I think there will rarely be a need to break compatibility with older engine versions while we are in feature freeze 21:05 MTDiscord late to the subject of things for 5.9, would it make sense to enable sdl2 by default now, so that more bugs get reported/fixed? 22:49 MTDiscord sfant: I think you should make it the opposite, it's only compatible with it's version number. And we can call it something kind of cool like v580-12-8-23-0 which will tell you the engine number, the date, and the build of that date in case there are multiple prs that go in on that date so you can line up to a really specific version