Closed Bug 424810 Opened 18 years ago Closed 18 years ago

Allow 3.0b5 and 3.0pre as Firefox maxVersions

Categories

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

Product:
addons.mozilla.org Graveyard
Component:
Administration
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: mossop, Assigned: clouserw)

Details

Can we allow 3.0b5 and 3.0pre (the trunk versions post 3.0b5) as maxVersions for Firefox so authors can get their addons updated in advance of the b5 release.
According to the email thread, we're waiting until 3.0b5 is released before adding 3.0b5 and 3.0pre. I agree that we should add 3.0b5 in advance of it being released though, so I think we should add 3.0b5 now and after it is released, add 3.0pre. Basil, do you agree, and if so, can you modify the blog post?
Component: Developer Pages → Administration
QA Contact: developers → administration
The question is when the version will change on trunk. I think it is likely that will change before b5 is released (after the b5 release has been tagged but before it has gone through all the final QA).
The trunk version is changing to 3.0pre in literally moments per the patch in bug 424242. Can we start accepting on AMO?
Added version 3.0pre
Assignee: nobody → clouserw
and 3.0b5
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.