Minetest logo

IRC log for #minetest-dev, 2023-11-30

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

All times shown according to UTC.

Time Nick Message
01:05 ShadowBot joined #minetest-dev
01:20 v-rob joined #minetest-dev
03:46 v-rob joined #minetest-dev
05:00 MTDiscord joined #minetest-dev
05:18 fluxionary joined #minetest-dev
06:00 MTDiscord <greenxenith> Merge and release tomorrow mayhaps?
07:09 calcul0n joined #minetest-dev
08:40 appguru joined #minetest-dev
10:13 MTDiscord joined #minetest-dev
10:17 Thomas-S joined #minetest-dev
10:17 Thomas-S joined #minetest-dev
10:25 [MTMatrix] <Zughy> https://github.com/minetest/minetest/issues/14049#issuecomment-1833482239
13:58 turtleman joined #minetest-dev
14:04 appguru joined #minetest-dev
14:46 Noisytoot joined #minetest-dev
15:16 Desour joined #minetest-dev
16:54 imi joined #minetest-dev
18:21 fluxionary joined #minetest-dev
18:22 v-rob joined #minetest-dev
18:35 Desour_ joined #minetest-dev
19:40 v-rob joined #minetest-dev
19:50 appguru joined #minetest-dev
20:16 Desour joined #minetest-dev
20:46 v-rob joined #minetest-dev
21:00 cranez joined #minetest-dev
21:31 YuGiOhJCJ joined #minetest-dev
22:07 MTDiscord <greenxenith> Sooo uh
22:07 MTDiscord <greenxenith> 5.8 milestones are done
22:10 MTDiscord <luatic> time for advent of minetest
22:15 MTDiscord <wsor4035> nope: https://github.com/minetest/minetest/pull/14059
22:15 Desour there's #14059. and we need an irrlicht revision for the android bugfix
22:15 ShadowBot https://github.com/minetest/minetest/issues/14059 -- Fix sound and particlespawner id generation by Desour
22:15 Desour and maybe also the android render thing
22:16 MTDiscord <greenxenith> Alright well nevermind then
22:16 Wuzzy joined #minetest-dev
22:17 grorp joined #minetest-dev
22:18 Desour let's make an advent calender, one minetest release each day
22:18 grorp we don't need an irrlicht revision for the android bugfix I think, https://github.com/minetest/minetest_android_deps/commit/575c4ae5146df6f19a1699941d14ca696e921593 should be enough
22:19 MTDiscord <luatic> Desour: Merge one PR per day? ^^
22:19 Desour oh, that would be actually interesting
22:22 grorp regarding "the android render thing", it's probably not that important, and sfan5 said that he thinks it's too risky this late
22:31 Desour then it's only the id fix that's left
22:31 Desour a revert could also work instead of my PR, just FYI
22:33 GreenXenith joined #minetest-dev
22:33 rubenwardy Seems odd to have merged such a nonblocking fix so close to release
22:34 v-rob joined #minetest-dev
22:34 MTDiscord <greenxenith> That would be my fault
22:36 MTDiscord <greenxenith> (I was trying to get things moving along; appears to have backfired)
22:43 Desour I mean merging bugfixes in feature freeze is fine, by definition, afaik
22:47 [MTMatrix] <Zughy> well, we've got an approval on #14059. Desour I guess you can merge
22:47 ShadowBot https://github.com/minetest/minetest/issues/14059 -- Fix sound and particlespawner id generation by Desour
22:48 [MTMatrix] <Zughy> Krock comment sounds also like an approval to me
22:52 Desour merging #14059 in 15
22:52 ShadowBot https://github.com/minetest/minetest/issues/14059 -- Fix sound and particlespawner id generation by Desour
22:53 MTDiscord <greenxenith> Isnt it a bit late for a release anyway? Its already late evening for those who are usually involved with that
22:54 [MTMatrix] <Zughy> Time will tell
22:54 MTDiscord <luatic> Can't tell if the core devs will have time, but I imagine a release on Friday evening or on the weekend would probably be the most realistic.
22:56 GreenXenith joined #minetest-dev
22:56 appguru joined #minetest-dev
22:57 sfan5 if we're aiming for a release today we have 3 minutes left
22:57 MTDiscord <greenxenith> Er, 1 hour and 3 minutes, by UTC
22:58 sfan5 the clock in my kitchen isn't utc
22:58 MTDiscord <greenxenith> Nor is mine
22:58 MTDiscord <greenxenith> But the jam goes by UTC
23:01 MTDiscord <luatic> ... and it's the 1st of December for me! 🎄
23:01 MTDiscord <greenxenith> The jam has used a latest stable version target at the start of the work time the last 2 years, and its a bit late to change that now, so I dont feel like I have much room to work with as far as qualifying 5.8
23:04 MTDiscord <greenxenith> I could technically stretch the definition to "the latest time in the world in which it is november", which would be an extra ... 14 hours?
23:06 MTDiscord <greenxenith> Making an exception for 5.8 specifically if this is a "it will definitely be released within the first few days of december" situation might be an option if I could somehow get a decent community concensus in the next ... hour :/
23:19 [MTMatrix] <Zughy> @greenxenith: I mean, there are no PRs/issues open, so it'll definitely be released within the first few days of December
23:20 [MTMatrix] <Zughy> personally I don't see the point of having a jam and not allowing the use of the new version. It can be a way to see some new things, e.g. people taking advantage of the new `start_time` sound parameter
23:22 MTDiscord <greenxenith> The point of targeting whatever version is stable at the start is to make it fair for developers
23:23 MTDiscord <greenxenith> Obviously I would prefer to target 5.8, but what if someone starts work with the notion that 5.8 isnt allowed, only to find out later
23:33 panwolfram joined #minetest-dev
23:34 Mantar Seems like something that could be cleared up with a forum post.
23:40 MTDiscord <greenxenith> I could mention it in the announcements, yeah
23:51 GreenXenith joined #minetest-dev
23:58 MTDiscord <greenxenith> one minute for someone to give me opinions
23:59 MTDiscord <greenxenith> do I take the gamble on 5.8 being released in the next day or two
23:59 MTDiscord <luatic> yes
23:59 ROllerozxa lol sure
23:59 Mantar there are RCs for it, people can dev on those
23:59 MTDiscord <wsor4035> this is minetest, when do we not take gambles?

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