Closed
Bug 627137
Opened 14 years ago
Closed 14 years ago
1.0b2 release blocker bugs
Categories
(Add-on SDK Graveyard :: General, defect)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: myk, Assigned: myk)
References
Details
This bug tracks code blockers for the Add-on SDK 1.0b2 release. Ping Myk, or comment here in this bug, to nominate a bug to block the release.
Comment 1•14 years ago
|
||
Does bug 628112 qualify, given that the Firefox nightly with the problem is going to be released as Firefox 4 b10?
Comment 2•14 years ago
|
||
And since I couldn't find it discussed anywhere, I also filed bug 628113.
Assignee | ||
Comment 3•14 years ago
|
||
(In reply to comment #1)
> Does bug 628112 qualify, given that the Firefox nightly with the problem is
> going to be released as Firefox 4 b10?
Hmm, based on the description of that bug, it certainly seems like a potential blocker. Adding it to the list pending further investigation.
Depends on: 628112
Assignee | ||
Comment 4•14 years ago
|
||
After further investigation, it looks like bug 628112 is not, as I feared, the consequence of a platform regression (or intended change) that has a significant impact on the SDK's functionality and requires working around or reworking in the SDK's code to accommodate the change.
Instead, it's just an existing (and probably longstanding) bug that happened to get exposed by a change to the platform. So it doesn't seem like a blocker for the next beta release. Removing it from the list.
No longer depends on: 628112
Assignee | ||
Comment 5•14 years ago
|
||
No blockers found, the release is on tap.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•