Closed Bug 353206 Opened 18 years ago Closed 17 years ago

Extension tracking for Firefox 2

Categories

(Firefox :: Extension Compatibility, defect)

Product:
Firefox
Component:
Extension Compatibility
Version:
2.0 Branch
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Milestone:
Firefox 2

People

(Reporter: chofmann, Unassigned)

References

(
URL
)

Details

(Keywords: meta)

tracking bug to make sure a good pct. of featured, most popular, and general extensions are ready for use when firefox 2 goes live. add individual bugs where exensions are know to not work...
url points at some testing status docs. many appear to have been fixed since beta 2.
URL: http://wiki.mozilla.org/Firefox2/L10n...
Depends on: 353207
nothing specific in the bug to block on, just for organizing a roll up of which extensions are not working, reviewing status, and making the general call about if extensions are in good enough shape to ship.
Flags: blocking-firefox2?
Depends on: 353250
Depends on: 353251
Depends on: 353253
No longer depends on: 353253
Keywords: meta
Summary: extension tracking for firefox 2. → Extension tracking for Firefox 2
Depends on: 353253
Depends on: 352906
Depends on: 353329
Flags: blocking-firefox2? → blocking-firefox2+
seems to occur in Minefield 3.0a1 also.
Component: General → Extension Compatibility
QA Contact: general → extension.compatibility
Depends on: 354209
Depends on: 354211
Depends on: 354212
Blocks: 354213
Depends on: 354215
Depends on: 354217
Is anything being done to let the authors of these extensions know about these problems? I glanced at a few of the bugs and no authors were CCed, and no extension authors are CCed on this tracking bug either. I see this effort as mostly pointless unless an effort is being made to talk with and inform the extension authors that their extension is incompatible.
No longer depends on: 354217
Depends on: 354218
Depends on: 354219
Depends on: 354221
Depends on: 354222
Depends on: 354225
Depends on: 354224
Depends on: 354227
Depends on: 354228
Depends on: 354230
Depends on: 354231
Depends on: 354233
Depends on: 354234
Depends on: 354236
Depends on: 354237
Depends on: 354238
Depends on: 354253
Depends on: 354254
Depends on: 354255
No longer blocks: 354213
Depends on: 354213
Depends on: 354257
Depends on: 354259
Depends on: 354260
Depends on: 354261
Depends on: 354263
Depends on: 354264
Depends on: 354265
Depends on: 354266
Depends on: 354268
Depends on: 354269
Depends on: 354270
The extension authors were not even notified (via a mail from AMO) that the release is very close. This means that those of them who don't follow the development process closely don't know they should be testing with Firefox 2 and updating their maxVersion. The mail shouldn't be sent just a few days before the release or you can't expect the extensions to even get the maxVersion bump (not talking about code-level fixes) by the time of release.
Nicolas, your rigtht. more information should have gone out further in advance; but we are going to try and get as many extensions working as possible in the short time we have before Firefox 2 release. cbeard has a message ready to go out to extension developers listed on amo.
adam, I'm going to make a pass through the bugs today and cc the extension owners where I can see that they have bugzilla accounts. then also try and start some testing to figure out if just a version update is needed or there are extension or core product bugs to be fixed. any help that folks can pitch in on this is welcome.
That's great to hear! BTW, I didn't mean my message to be negative. I meant to say that many extensions can be updated by their authors in time if you notify them soon instead of waiting for the RC or the final release.
Depends on: 353256
(The e-mail have been sent out. Nice idea about a t-shirt!)
yes, the notification was much later than intended (we had hoped to get this out well before the RC!) and we'll work hard now to engage with individual extension developers to work together to achieve compatibility with fx2
Depends on: 354571
Depends on: 354577
Depends on: 354579
Target Milestone: --- → Firefox 2
Depends on: 354932
Depends on: 354933
Depends on: 354972
No longer depends on: 354209
Depends on: 355401
Depends on: 355403
Depends on: 355405
Depends on: 355406
Depends on: 355504
Depends on: 355562
Depends on: 355563
Depends on: 355564
Depends on: 355566
Depends on: 355568
Depends on: 355571
Depends on: 355574
Depends on: 355579
Depends on: 355580
Depends on: 355582
Depends on: 355584
Depends on: 355586
Depends on: 355587
Depends on: 355588
Depends on: 355678
Depends on: 355679
Depends on: 355681
Depends on: 355682
Depends on: 355683
Depends on: 355684
Depends on: 355685
Depends on: 355686
Depends on: 355687
Depends on: 355688
No longer depends on: 355689
Depends on: 355690
Depends on: 355691
Depends on: 355692
Depends on: 355693
Depends on: 355694
Depends on: 355695
Depends on: 355696
Depends on: 355697
Depends on: 355698
Depends on: 355700
Depends on: 355701
Depends on: 355702
Depends on: 355703
Depends on: 355704
Depends on: 355727
Depends on: 355729
Depends on: 355730
Depends on: 355732
Depends on: 355734
Could someone please define what a popular extension is in a number of downloads? Would be fine for filling in missing extensions. Thanks
Depends on: 356167
Depends on: 356170
Depends on: 356181
Depends on: 356197
Blocks: 356315
Blocks: 356318
Depends on: 356320
No longer blocks: 356318
Depends on: 356318
Depends on: 356323
No longer blocks: 356315
Depends on: 356315
Depends on: 356324
Depends on: 356367
so here are some estimates of where we ended up for extension compatiblity on the day of fx2 shipping. 563 compat with 2.0.0.* 167 3.0a1 730 are looing good for fx2 release! another 40 are compat with "2" and need to be investigated for updates 55 are at 2.0a1 - 2.0b2 and might be updated soon. about 417 never made it past 1.0.7 compatability.... a lot of extensions have a short life... 727 are still at 1.5.0.* I expect that like the 1.0.x series of extensions many of these 727 might not be upgraded or need to be upgraded to 2.0.0*+ compatiblity because of features included in the core product, or otherwise have become obsolete or unmaintained. Thanks to all that helped out with getting to a new level of extension compatiblity before a major release.
one more stat - 73 out of the top 115 under this tracking bug made it to compatabiliy with fx2 in time for the release.
Cameron fixed the 40 with firefox "2" so 770 is the number of 2.0.0.* extensions
Depends on: 360056
Flags: blocking-firefox2+
Depends on: 363320
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.