Closed
Bug 598788
Opened 14 years ago
Closed 14 years ago
make SDK's Firefox maxVersion reflect actual max version it supports (4.0b6)
Categories
(Add-on SDK Graveyard :: General, defect)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: myk, Assigned: myk)
Details
Attachments
(1 file)
824 bytes,
patch
|
avarma
:
review+
|
Details | Diff | Splinter Review |
We typically make the SDK build addons whose Firefox maxVersion is the highest maxVersion AMO supports, because we test the SDK against the most recent nightly builds of Firefox. Currently that maxVersion is 4.0b8pre. But for the 0.8 release, we have decided to support only the most recently beta release, 4.0b6, because the tree is so unstable as the Firefox/Gecko teams land a bunch of stuff in preparation for the feature freeze. Thus the SDK's Firefox maxVersion should reflect that decision and change from 4.0b8pre to 4.0b6. Here is the patch that makes the change.
Attachment #477747 -
Flags: review?(avarma)
Updated•14 years ago
|
Attachment #477747 -
Flags: review?(avarma) → review+
Assignee | ||
Comment 1•14 years ago
|
||
Fixed by changeset https://hg.mozilla.org/labs/jetpack-sdk/rev/4e9192e853b6.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 2•14 years ago
|
||
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product. To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
You need to log in
before you can comment on or make changes to this bug.
Description
•