Inconsistent compatibility version enforcement #363
Description
Hello,
I am the developer of the following plugin, that is based on the calendar experiment .
I noticed that the strict_max_version rule enforcement is inconsistent across the different options Thunderbird offers.
When I upload the ZIP with a new version of my plugin through Thunderbird submission page , the strict_max_version must be explicitly given with a major existing version e.g. 140.* is allowed, 140.0.1 is allowed, * is not (no major), 149.* is not (not released). It is justified in the error message by its dependency to an experiment. It's understandable but quite heavy on maintenance effort to upgrade to each version by uploading a new plugin version with (solely) an updated manifest.json.
Turns out, from the add-on management page, I can change strict_max_version without restriction . I find it very handy as a developer to be able to have * accepted (even with experiments). https://addons.thunderbird.net/en-US/developers/addon/events-from-mail-content/versions/2500699
