On Sun, 1 Jun 2025 10:56:58 +0200 Kristian Amlie <krist...@amlie.name> wrote:
>On 31.05.2025 13:47, ichthyo wrote: >> On 31.05.25 10:41, Kristian Amlie wrote: >>> I would follow the semantic versioning mantra: Warn when major is >>> different, and when minor is higher, otherwise don't warn. >> >> So to summarise: Kristian you propose the following change: >> >> - remove the more elaborate check >> >> - rather define "Incompatible" as major differs or minor of the >> config is higher than current software >> >> - never save automatically for migration any more, just warn > >Correct! I've just come back from a sunlit walk through a favourite woodland to clear my thoughts, and it occurs to me we've all been rather overthinking this. The base config hasn't changed for ages, and is not likely to. That has the most important settings. Most of config is far from critical and although it might be a bit inconvenient if some parts get changed (very rarely), it's not a problem when new features are added. What *would* be annoying for anyone would be the same warning being repeated on every startup, so is there a way we can ensure that this only happens once on version changes. -- Will J Godfrey _______________________________________________ Yoshimi-devel mailing list Yoshimi-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
