alienvalkyrie alienvalkyrie Should we already do this for 3.1? I think it's unlikely anyone is using mixed format versions during their ruleset update process, but if they are, sticking to 3.2 would leave them more time to adapt.
alienvalkyrie Reply To alienvalkyrie
Should we already do this for 3.1? I think it's unlikely anyone is using mixed format versions during their ruleset update process, but if they are, sticking to 3.2 would leave them more time to adapt.
I'll go ahead and stick with that, then.
alienvalkyrie alienvalkyrie Backported to S3_1: #44203
Alina L. wrote about ruleset format versions in https://www.hostedredmine.com/issues/695469
"which file's version should be checked? All possibly relevant ones (and hope they don't disagree)?"
--
We probably shouldn't try to support rulesets where the individual files disagree on version. I'd suggest replacing separate version numbers in rscompat_info with just one version, checking that all files agree (where we currently fill compat->ver_...), and considering it a hard ruleset loading failure when they don't.