Time  Nick      Message
16:25 ZenonSeth so is the 5.18 feature freeze gone, cause #17710 looks ready to merge
16:25 ShadowBot https://github.com/luanti-org/luanti/issues/17710 -- Refactor mesh caching by appgurueu
16:57 sfan5     yes
16:57 sfan5     by definition the 5.18 feature freeze can't extend past the release of 5.18
16:59 ZenonSeth yes i suppose i was more asking about extended feature freeze in case a critical bug is found and 5.18.1 needs to be released or something
17:00 ZenonSeth in any case, I'm going to go through and do some code reviews this week, trying to figure out what PRs are a high prio myself - but if anyone want to use the PR Prioritization project to put some up there, I can follow those too
17:01 sfan5     we can (and do) base patch releases on the release tag directly, so no need to keep master clean
17:01 ZenonSeth nice, ok
17:08 ZenonSeth i did wonder why you don't branch off master for releases, but i suppose keeping history straight is easier when there's no dedicated team to handle merging back or requiring 2prs per fix etc
17:47 Krock     backport branches can (and did) exist separately. after merge to stable-XX they're then removed
17:48 Krock     though the 0.4.17(.1) release is already a few years ago
22:56 ZenonSeth btw can i also add things to upcoming release milestones, or is there a process or something ?
22:59 sfan5     there's no process no
23:00 sfan5     I generally add stuff when I think "we shouldn't forget to merge this next release"
23:01 ZenonSeth makes sense. my thiking was it would be nice to see at least some progress towards SSCSM every release, and #17331 is fairly non-controversial i think
23:01 ShadowBot https://github.com/luanti-org/luanti/issues/17331 -- SSCSM: Add sscsm api for hud elements, mirroring csm api by ZenonSeth