Closed Bug 574383 Opened 15 years ago Closed 15 years ago

Release Compatibility Reporter for Trunk / Firefox 4.0

Categories

(addons.mozilla.org Graveyard :: Compatibility Tools, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jbecerra, Assigned: fligtar)

Details

(Whiteboard: [not needed for code freeze])

In preparation for Fx 4 beta 1 we need the add-on compatibility reporter to be compatible with the trunk and what will become 4.0 beta 1, and so on.
Dupe of 564870? I think this bug should be about making sure that it's: - submitted to AMO with a maxVer of 4.0* - approved
This is just waiting on QA to finish testing and then it'll be added to AMO. I'm fine with this as a tracking bug to doing that though.
Assignee: nobody → fligtar
(Not a code freeze blocker, but want to get it on the tracking list for before-we-release-beta-1)
blocking2.0: --- → beta1+
Whiteboard: [not needed for code freeze]
Currently the maxVer is 3.7a6pre which is not very Firefox 4 friendly. What's the max that AMO accepts?
We'll use 3.7a6pre until 4.0b1 is added for everyone and then I'll bump it.
This is a significant release so I suggest a version # for the add-on of 0.5 or even 1.0.
Summary: compatibility reporter needs to be compatible with 3.7 and/or 4.0 → Release Compatibility Reporter for Trunk / Firefox 4.0
(In reply to comment #4) > Currently the maxVer is 3.7a6pre The version at https://addons.mozilla.org/en-US/firefox/addon/15003/ is 3.7a4, unless I miss something.
There is a test version up on http://dl.dropbox.com/u/2575442/acr.xpi I will run tests against it today to make sure it works as expected for the release.
(In reply to comment #7) > The version at https://addons.mozilla.org/en-US/firefox/addon/15003/ is 3.7a4, > unless I miss something. Odd, I thought I bumped that down a couple of weeks ago. Justin? The new version coming should have that.
Today I have checked all resolved bugs. I had to file a couple of new bugs on topics I have discovered when testing the add-on. Justin please revise those bugs.
What's the ETA on this? This is one of the big tools that Beta Testers rely on. Especially given what's happening with Nightly Tester Tools etc.
(In reply to comment #9) > (In reply to comment #7) > > The version at https://addons.mozilla.org/en-US/firefox/addon/15003/ is 3.7a4, > > unless I miss something. > > Odd, I thought I bumped that down a couple of weeks ago. Justin? > > The new version coming should have that. Do we also have to change the maxVersion inside the install.rdf itself? Or do we always check AMO? With the version bump to 4.0b1 we would need an update.
We also would need a new pref to override the compatibility: "extensions.checkCompatibility.4.0b"
Okay, I bumped the version to 0.5, updated compatibility to 4.0b2pre, and added the two manual preferences for 4.0b and 4.0pre in r69825. Here's a test build: http://people.mozilla.com/~fligtar/acr/acr-0.5.xpi I'd like to release this later today unless there are any objections.
(In reply to comment #14) > Okay, I bumped the version to 0.5, updated compatibility to 4.0b2pre, and added > the two manual preferences for 4.0b and 4.0pre in r69825. Shouldn't that be 4.0b and 4.0p these days? Pretty sure the "extensions.checkCompatibility.4.0pre" won't work any more (you could verify with Mossop).
Tested version 0.5 and it looks good so far. (In reply to comment #15) > > the two manual preferences for 4.0b and 4.0pre in r69825. > > Shouldn't that be 4.0b and 4.0p these days? > > Pretty sure the "extensions.checkCompatibility.4.0pre" won't work any more (you > could verify with Mossop). CC'ing Dave so we can get an answer.
Status: NEW → ASSIGNED
In the interest of time, I added the other pref as well, which is what we'd been doing previously. After we get a definite answer we can remove the unnecessary prefs. I just uploaded version 0.5 to AMO and it should show up after the cache clears shortly. https://addons.mozilla.org/en-US/firefox/addon/15003/ Thanks everyone!
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Looks good. Marking as verified fixed.
Status: RESOLVED → VERIFIED
Hardware: x86 → All
(In reply to comment #15) > (In reply to comment #14) > > Okay, I bumped the version to 0.5, updated compatibility to 4.0b2pre, and added > > the two manual preferences for 4.0b and 4.0pre in r69825. > > Shouldn't that be 4.0b and 4.0p these days? > > Pretty sure the "extensions.checkCompatibility.4.0pre" won't work any more (you > could verify with Mossop). I should be extensions.checkCompatibility.4.0pre per bug 538234
(In reply to comment #19) > I should be extensions.checkCompatibility.4.0pre per bug 538234 My bad. Sorry for the fire drill (I read bug 538234 back when it landed...guess I got confused by Alice's comment there. Note to self: read the code next time).
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.