369742 - AMO should allow for a version that covers trunk but not releases (or betas?)

Status: RESOLVED WONTFIX

(addons.mozilla.org Graveyard :: Administration, enhancement)

Description

[:Gijs (he/him)]

OK. The problem, at least from my point of view, is that it's thoroughly annoying to keep updating one's extension to support the newest alpha version (updates of the extension will need the correct thing in their install.rdf, or the upload will bork, and you need to keep updating the version in the control panel once you've released a version, and the admins need to keep adding new alpha versions, etc.).

Wouldn't it be a lot easier for all involved to just use one alpha version, say, 3.0a1000, so we don't have these problems at all? The likeliness of something breaking during an alpha cycle isn't any different from the likeliness of breaking when the alpha is released as such, and it doesn't make sense to me to burden everyone involved with extra formalities that don't seem to serve any real purpose.

Ideally, I'd personally like something that includes the beta releases as well, but I'm not sure if that's possible (could we specify 3.0b100?)

Comment 1

[Mike Shaver (:shaver -- probably not reading bugmail closely)]

I'm not sure that we actually want to do this, or that I agree with the reasoning in the second sentence of the second paragraph, but I _am_ sure that it's pretty minor.

Comment 3

[Justin Scott [:fligtar]]

Responding to Al's bug since I was cc'd on it: I have never understood why we restrict versions at all, so you have my vote.

I added Firefox 3.0b1 and 3.0.0.* earlier today, the latter because I couldn't come up with an argument for Stuart saying that yes, he did know for a fact that his extension was compatible with 3.0.0.* and that it wouldn't break before then because he controls the code it uses.