Prevent developers from setting minversion and maxversion in a way which contains unreleased appversions with API- or UI-changes. At the moment, AMO allows setting - a range like 2.0 - 3.1a1pre for Thunderbird, but 3.0* API and UI haven't been frozen, so this will cause broken compatible add-ons - a range like 3.0 - 3.2a1pre for Firefox there only the API has been frozen With implementation of bug 342963 (needs bug 301236), this could be fixed. At least we need a policy what to do now with updates with the maxVersion on (in?) trunk.
We'll deal with this if/when add-ons break. Putting the decision in the hands of the developer is the simplest thing and should work in 99% of the cases.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.