Extension tracking for Thunderbird 2

RESOLVED INVALID

Status

Thunderbird
General
RESOLVED INVALID
10 years ago
10 years ago

People

(Reporter: tonymec, Unassigned)

Tracking

({meta})

Firefox Tracking Flags

(Not tracked)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008030401 SeaMonkey/2.0a1pre
Build Identifier: Thunderbird 2.0.0.*

This is a tracking bug, to track featured, most popular, general, etc. extensions which would have stopped working with Thunderbird 2. The equivalent Firefox bug is bug 353206.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.



I was surprised not to find any "Extension Compatibility" component for the "Thunderbird" product.
Keywords: meta
Version: unspecified → 2.0
You seem to have missed the point of bug 353206, which was to track whether enough of the most popular extensions were compatible to allow shipping without the risk of people deciding to not upgrade because their favorite extensions wouldn't work. It's going on a year too late to make the call about whether we should ship Tb 2 based on which extensions are or are not compatible.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
I noticed the Firefox bug was still open long after Firefox 2.0 had been shipped, and I assumed it would continue to track browser support by extensions as long as Firefox 2 would be supported.

Also, I asked first on newsgroup mozilla.dev.planning whether such a tracking bug as this one (or the same for Tb3), if I opened them, would be resolved INVALID or WORKSFORME, and I only opened it after Dan Mosedale assured me that they wouldn't. Alex Polvi, to whom the Firefox tracking bugs are assigned, and who had intervened earlier in the same thread, didn't contradict him.

Comment 3

10 years ago
I wouldn't go quite so far as to say that I made an assurance, but I do agree that this is a useful bug to have around.  In particular, I think it's worthwhile to have an easy way to track / evangelize as-yet-not-updated extensions independent of the Thunderbird 2 release.  REOPENing for now; but I'm open to be being convinced that I'm not thinking about this the right way...
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---

Comment 4

10 years ago
Ah, I see that there's already been substantial discussion about this in dev.planning; reading that now...

Comment 5

10 years ago
OK, Phil's thinking that we need a component for extension compatibility before it gets opened and used sounds right to me.  Putting things back the way they were.  Tony, it sounds like Phil and I agree that it would be reasonable for you to create the component he talked about in the newsgroup and then re-open this if you still want to track things here.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago10 years ago
Resolution: --- → INVALID
(In reply to comment #5)
> OK, Phil's thinking that we need a component for extension compatibility before
> it gets opened and used sounds right to me.  Putting things back the way they
> were.  Tony, it sounds like Phil and I agree that it would be reasonable for
> you to create the component he talked about in the newsgroup and then re-open
> this if you still want to track things here.
> 

I'm moving away from Thunderbird anyway; and a similar request to add a component to the Mozilla Suite got RESOLVED WONTFIX -- apparently it was the right time by respect to neither SeaMonkey nor the Bugzilla database.

Anyone wants to create the Bugzilla component (Thunderbird/Extension compatibility), reopen this bug, and have it ASSIGNED to him, go ahead with my blessing.
You need to log in before you can comment on or make changes to this bug.