Closed Bug 701107 Opened 11 years ago Closed 11 years ago

Bump Nightly Tester Tools extension's maxVersion to support Firefox 11.*, Thunderbird 11.*, SeaMonkey 2.8.*

Categories

(Other Applications Graveyard :: Nightly Tester Tools, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: r4162821-mozbugzilla, Assigned: tonymec)

References

Details

Attachments

(1 file)

2.53 KB, application/octet-stream
Details
Attached file install.rdf
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0a1) Gecko/20111109 Firefox/11.0a1 Firefox/11.0a1
Build ID: 20111109031111

Steps to reproduce:

1)Download NTT Version 3.2, Firefox 11.0a1 complains that it is not supported with FF 11.0a1 (nightly 2011-11-09_031111); a nightly build.

2)RightClick on Add-ons Tab in Nightly frame, download to a File Location, I Chose c:/My Downloads/FF/AddOns/Nightly Tester Tools/3.2

Save XPI file to new folder for ver 3.2

3) Open Ver 3.2 file with 7-ZIP, expand to sub-folder , 'extract',

4) Open Text Editor Notepad Plus, Read file 'install.rdf', change value  'maxVersion'  to '99a0' , for firefox only component. reason: If FF Nightly Tools are to work with Nightly Builds, then Max version should be impossible to reach. , and 99a0 is 1 character shorter than 100a0., as other Bug fix tools use.

Re-Zip Export Tree, rename New Zip file from .zip to 'nightly_tester_tools-3.2-fx+tb+sm.xpi' ,BUT save in a separate directory , '3.2.1',

Open FF Add-Ons, Click on Tools Button, 'Open Add-on from file', Point to NEW file at 3.2.1, and Voila!


Actual results:

Initial Zip, failed with error on corruption of XPI file.

(Was using 7z compression instead of zip compression)

-Re-Zipped to zip compressor, then saved as 3.2.1 patched file.

-Runs fine.


Expected results:

File *SHOULD* work with Nightly Builds.

--see attached install .rdf
Severity: normal → major
Upgraded Bug to MAJOR , IMHO as if NTT fails to work in a test environment, and it is a TOOL (Program , Utility, APP etc), then it should be renamed to FF Tester Tools, instead of NIGHTLy, as this NAME gives the impression that it will work with all Builds of FF.
(In reply to Richard Rieger from comment #1)
> Upgraded Bug to MAJOR , IMHO as if NTT fails to work in a test environment,
> and it is a TOOL (Program , Utility, APP etc), then it should be renamed to
> FF Tester Tools, instead of NIGHTLy, as this NAME gives the impression that
> it will work with all Builds of FF.

Actually, the name was given long before Minefield was renamed Nightly; "nightly" in "nightly tester tools" applies to the new builds made each night for (at that time) all code branches of Firefox, Thunderbird, SeaMonkey, etc., which weren't yet at end-of-life.

This said, whenever the version number of an application is increased, lots of extensions become "incompatible", especially on what used to be called the trunk, and still is except for Firefox, where it's now called "Nightly" with a capital N (so that every night, the Firefox build machines compile as many "Nightly nightlies" as there are supported platforms — silly name if you ask me, but I didn't have any voice in the matter). It is for this very reason that the Add-on Compatibility Reporter extension was developed: if you install it, the addon manager (about:addons) will still tell you which extensions don't advertise compatibility with the current application version, but it won't anymore act on these incompatibilities: there will be no auto-disabling.

And yes, NTT works (AFAICT) with the new Toolkit 11 builds (such as SeaMonkey 2.8a1 which I am using) so IMHO it would benefit by a version bump.
Severity: major → normal
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Nightly Tester Tools Plugin fails with upgrade to Version 11.0a1 (Nightly 2011-11-09) → Bump Nightly Tester Tools extension's maxVersion to support Firefox 11.*, Thunderbird 11.*, SeaMonkey 2.8.*
P.S. The Add-on Compatibility Reporter doesn't advertise compatibility with (at least) SeaMonkey 2.8a1: you may need to set extensions.checkCompatibility.nightly to false in about:config (probably creating the pref with "Right-click → New → Boolean" in the process) before you can install it in the new Nightly (or Shredder, or SeaMonkey trunk) nightlies.
Assignee: nobody → antoine.mechelynck
Status: NEW → ASSIGNED
The maxVersion settings have been fixed on the AMO site. Installing NTT ought to work now (if you do it while connected to the Internet and with the browser not set to Offline mode).
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Blocks: 712658
Depends on: 663272
Downloaded NTT from
https://addons.mozilla.org/en-US/thunderbird/addon/nightly-tester-tools/?src=search;

Ran a Zip expand on the XPI file for importing to TB 11, checked install.rdf -date 2011-11-01;

TB:10a1
FF:10a1
SM:2.7a1

are the MaxVersions that are listed in the (new) RDF.

Paste of BuilID  Copy:
Mozilla/5.0 (Windows NT 5.1; rv:12.0a1) Gecko/20111223 Firefox/12.0a1 Firefox/12.0a1 ID:20111223032107
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
In reply to comment #5:
What counts is what compatibility range AMO knows for the extension: you can see that by unfolding the "Version information" foldout at the bottom of the exteznsion page.

If you install this extension with an open connection to the Internet, Thunderbird should ask AMO for the compatibility data, and accept that in preference to what is found in the install.rdf.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → WORKSFORME
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.