Michal Vašut
Michal Vašut
Sure, therefore I've created the issue - not to necessarily solve it immediately, but to not forget it. 😉
Yeah that's exactly this - moving to commns (or generalizing it) - store settings But there are few other things on my stack, that imho needs to be done before...
Yop, great idea!
Fun fact: > Since version 3, TeX (the typesetting system) has used an idiosyncratic version numbering system, where updates have been indicated by adding an extra digit at the end...
Btw, there is more standardized solution, check [Semantic Versioning](https://semver.org/).
I'm not really for Tree.js releases. Maybe even for specific views. I would suggest different thing that would be totally optional. What about to add readme.md file to each view...
``` # Release notes 2022-10-14 - added feature 1 - redactored xyz ``` This commented out text is not rendered by Github (when not in codeblock), but still perfectly parseable...
IMHO what Przemek said is correct - for end user, it doesn't really matter how it is embedded into the app, the only issue is different visual style (look &...
Sure, I'll make some docs today and we can discuss the parameters later. On Tue, Oct 11, 2022, 17:27 Brian Casey ***@***.***> wrote: > We'd like to have some guidelines...
Better use this variant https://en.m.wikipedia.org/wiki/Daitch%E2%80%93Mokotoff_Soundex Standard soundex is unusable for non-English names.