Time Nick Message 01:08 MTDiscord just my two bent pennies, feel free to ignore this/tell me to pound sand, but would like to see more "version" notes in docs. what this means is just annotating $thing with $thing since version $y or something, rather than just putting $x 01:09 MTDiscord That's a very good idea. 01:09 MTDiscord Except figuring out which version something was added in is work. 01:09 MTDiscord in case my two bent pennies didnt come accross right, see https://dev.luanti.org/database-backends/#backend-comparison-table where mod storage has version numbers 01:10 MTDiscord perhaps, but take for example https://github.com/minetest/dev.luanti.org/issues/126, its something new in 5.11, if be written now, then you already know. not much extra work 01:10 MTDiscord Especially since the accurate way to annotate it would be "$thing since version x with bug, since version y with other bug, fixed since version z, with first bug again since undetermined version." 01:12 MTDiscord meh, thats kinda over complicating it. more so just bare minimum of when stuff shows up. for example with the db stuff, it prevents idiot me working on some cursed old version (say 5.1) from trying to migrate to postgresql and then complaining it doesnt work. possibly also going and wasting other peoples time asking why 01:15 MTDiscord . 01:15 MTDiscord cppreference is a great example of that. Each feature or API change is labelled with the version of the standard where it was introduced. 01:16 MTDiscord also mdn caniuse section at the bottom 15:39 MTDiscord @wsor this sounds like something that should be tracked in an issue 😉 15:41 MTDiscord Meh, potential guidelines maybe 18:03 MTDiscord I don't think this should be a requirement, just a suggestion.