Time Nick Message 00:22 paramat #8418 is ready 00:22 ShadowBot https://github.com/minetest/minetest/issues/8418 -- Require 'waving = 3' in nodedefs to enable liquid waving shader by paramat 10:00 Krock puhsing https://krock-works.uk.to/u/patches/0001-Use-group-stick-in-recipes-fixes-2306.patch in 15 minutes 10:16 Krock pushing 13:57 nerzhul nice 15:47 Krock #8351 needs a second approval. simple performance improvement 15:47 ShadowBot https://github.com/minetest/minetest/issues/8351 -- Improve core.after in a simple way by DS-Minetest 15:50 Krock #8368 too 15:50 ShadowBot https://github.com/minetest/minetest/issues/8368 -- Add node field to PlayerHPChangeReason table by pauloue 15:54 Krock nerzhul: do you have any comments on #8350? 15:54 ShadowBot https://github.com/minetest/minetest/issues/8350 -- Damage: Play no damage sound when immortal by SmallJoker 17:05 rubenwardy nerzhul, Krock: #8420 updated 17:05 ShadowBot https://github.com/minetest/minetest/issues/8420 -- Prevent multi-line chat messages server-side by rubenwardy 17:24 p_gimeno it would be nice if lua_api.txt had an explanation for add_particle 17:26 p_gimeno it seems to return the input table, that's not documented either 20:04 paramat rubenwardy looks like #8420 can be merged 20:04 ShadowBot https://github.com/minetest/minetest/issues/8420 -- Prevent multi-line chat messages server-side by rubenwardy 20:06 paramat sfan5 and all shall we release 5.0.1 this evening? 20:06 sfan5 fine with me 20:08 GreenDimond Am I correct that the only real breaking changes I need to worry about on my server is attachment/positions and nodeupdate()? 20:10 paramat see https://dev.minetest.net/Changelog#0.4.16_.E2.86.92_5.0.0 'Breaking changes and deprecations' 20:10 GreenDimond That is what I am looking at 20:26 paramat depending on your server more changes may be needed, so we can't confirm 20:26 GreenDimond True 21:02 paramat rubenwardy are you available to release 5.0.1? 21:02 sfan5 paramat: do you intend to have a backport branch for mtg or just tag 5.0.1 on master? 21:06 rubenwardy what about the treasure fix? 21:06 rubenwardy and no, not tonight 21:06 rubenwardy I made the PR so there's a place to comment about 5.0.1 21:07 rubenwardy and write down commits to be included 21:07 rubenwardy other people can push to it etc 21:08 sfan5 1) I was talking about minetest_game 2) What is the "treasure fix"? 21:12 rubenwardy https://github.com/minetest/minetest_game/commit/02e2cab375a315eab310f64a4d3de6bee58ba61a 21:13 sfan5 i'd include it in 5.0.1 either way 21:14 rubenwardy looks like there's no features in MTG since 5.0.0 21:14 rubenwardy so I'm fine with tagging in master 21:14 rubenwardy but make sure the stable-5 branch is also 5.0.1 21:34 paramat i don't think MTG needs to mention 5.0.1 at all (does it?) as 5.0.1 is a bugfix on 5.0.0 and MTG needs no bugfixes 21:35 paramat the treasure fix isn't needed for MTG 5.0.0 21:36 sfan5 fixing a crash bug is not important? 21:37 paramat if a 5.0.1 tag is added, add it to the same commit as MTG 5.0.0? 21:37 paramat the crash is caused by a commit added after 5.0.0 21:38 paramat i'm saying MT 5.0.1 should use MTG 5.0.0 21:38 paramat or be tagged as that 21:38 paramat oh hang on 21:38 paramat sorry 21:39 * paramat is in 'detached head state' 21:39 paramat MTG 5.0.0 does crash on unknown items 21:44 paramat hmmm 21:45 paramat latest MTG is good for using in MT 5.0.1 21:45 paramat hmm then it will need a tag 21:46 paramat tagging 5.0.1 on master seems good 21:47 paramat seems ruben doesn't have time tonight so perhaps release tomorrow evening 21:56 paramat 8420 isn't ready anyway 22:49 benrob0329 Proposal: Ship MTG via the content store, not directly in the package 22:59 paramat i'm not keen on that idea 23:00 benrob0329 It would help separate MT from MTG, and would even allow them to have separate release schedules 23:21 kaeza Oh, docker container... 23:22 kaeza Oops, won't chan. 23:23 kaeza Wrong even.