Closed Bug 504153 Opened 15 years ago Closed 15 years ago

Update DOMi compat info for SeaMonkey 2.0b2 and Thunderbird 3.0b4

Categories

(Other Applications :: DOM Inspector, defect)

Product:
Other Applications
Component:
DOM Inspector
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kairo, Unassigned)

References

(
URL
)

Details

Current DOMi should be updated to be compatible with up to SeaMonkey 2.0b2 and Thunderbird 3.0b4 both in the install.rdf on trunk and the AMO settings for the latest version.

We should keep up what we did with SM2.0b1 and not use the "pre" there, so we'll be compatible without further change with the upcoming release when cutting it. If we use the version number of 2.0b2 without the "pre" now, that should work fine once again (same for TB). :)
First we have blanket rs from sdwilsh for version updates so I'm not even sure we really need a bug for this.

Second I was going to object to not using the pre on the basis that things can change which could break DOMI. However, as 1.9.1 is now stable, that doesn't apply. Although on amo I'll still be recommending that TB is pre until near b4.
(In reply to comment #1)
> Although on amo I'll still be recommending that TB is pre until near b4.

I meant to say "that TB has a max version which is 3.0b4pre until near b4" because of the expected API changes.
(In reply to comment #1)
> First we have blanket rs from sdwilsh for version updates so I'm not even sure
> we really need a bug for this.

We may not formally need it, but a bug is always a good way of tracking that it actually does happen.

> Second I was going to object to not using the pre on the basis that things can
> change which could break DOMI. However, as 1.9.1 is now stable, that doesn't
> apply. Although on amo I'll still be recommending that TB is pre until near b4.

OK, we can keep TB at 3.0b4pre, but I'd like SeaMonkey to be at 2.0b2 as we never had an incompatibility problem yet but we had the unfortunate incidents where we forgot to change to the non-pre version until after tagging had been done, and I don't want to run into that again.
Actually, we probably should go right to 2.1a1pre for SeaMonkey, so that DOMi works on mozilla-central-based versions as well (and that automatically makes it work for all 2.0 versions anyhow).
This has been fixed by bug 504713 and bug 479290
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.