343473 - Allow maxversion of 2.0.0.* or 2.*

Status: RESOLVED WONTFIX

(addons.mozilla.org Graveyard :: Developer Pages, defect)

Description

[Aaron P]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a3) Gecko/20060626 BonEcho/2.0a3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a3) Gecko/20060626 BonEcho/2.0a3

As of 2006-07-03, the highest maxversion allowed at AMO for extensions is 2.0a3. There needs to be a way to set the maxversion to a value that will allow the extension to install in 2.0.0.0 final. We aren't that far off from a 2.0 release and people who want to update their extensions early cannot do this.

P.S. The same is true for Firefox 3.0, 3.0.0.*, 3.* 

Reproducible: Always

Steps to Reproduce:
1. Log into AMO as a developer
2. Set the maxversion of your extension to 2.0.0.* and create the xpi
3. Add the xpi as a new or updated extension


Actual Results:  
Error message: "Error! The MaxAppVer for Firefox of 2.0.0.* in install.rdf is invalid."

Expected Results:  
The maxversion is accepted.

The maxversions of 2.0.0.* and 2.* work fine in Firefox itself.

Comment 1

[alanjstr]

Firefox 2.0 is still in alpha.  I would wait until beta before worrying about final.

Comment 2

[Mike Shaver (:shaver emeritus)]

We permit 2.0b1 today (or will by the end of today), and will add 2.0 version support when  the Firefox team believes that we're frozen enough that extension authors can actually know that their extension will work with Fx2.  We don't want extensions in the wild that claim support for Fx2 resulting in a broken upgrade experience if it turns out that the author guessed incorrectly.

The 2.0b1 version (and corresponding 3.0a1) should permit anyone using a current Fx2 or Fx3 pre-build to install and test extensions without problem.