My original intent for these fields was that they would be a "contains" match by default, not an exact match. So "140" would match any version containing "140". That can cause some unfortunate ambiguities in edge cases but I think the general idea is still good, and maybe we could introduce the "*" wildcard operator for all targeting fields. So "140.*" would cover all ESR versions past and future. "en*" would cover all English locales, etc.
Bug 1958119 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
My original intent for these fields was that they would be a "contains" match by default, not an exact match. So "140" would match any version containing "140". That can cause some unfortunate ambiguities in edge cases but I think the general idea is still good, and maybe we could introduce the "\*" wildcard operator for all targeting fields. So "140.\*" would cover all ESR versions past and future. "en*" would cover all English locales, etc.
My original intent for these fields was that they would be a "contains" match by default, not an exact match. So "140" would match any version containing "140". That can cause some unfortunate ambiguities in edge cases but I think the general idea is still good, and maybe we could introduce the "\*" wildcard operator for all targeting fields. So "140.\*" would cover all ESR versions past and future. "en\*" would cover all English locales, etc.