Closed Bug 755073 Opened 13 years ago Closed 13 years ago

Block htc desire on the play market for beta 1

Categories

(Release Engineering :: Release Requests, defect)

ARM
Android
defect
Not set
normal

Tracking

(firefox14 fixed, blocking-fennec1.0 beta+)

RESOLVED FIXED
Tracking Status
firefox14 --- fixed
blocking-fennec1.0 --- beta+

People

(Reporter: kbrosnan, Assigned: mozilla)

References

Details

Attachments

(3 files)

The HTC Desire gets only white pages on Beta 1. This is working correctly on today's Aurora build. So do we want to block the Desire for beta 1?
It would be nice to know what was patched and checked in that caused this behaviour and fixed this behaviour.
FWIW, the Desire is a pretty popular device and it is also in the range of hardware specs where we might get more bugs, so having it available for beta testing can get us high value bugs that affect more people. My recommendation is that we have it for beta and if we can't get it for beta 1,have a plan to whitelist it as soon as possible.
(In reply to Irina Sandu from comment #2) > My recommendation is that we have it for beta and if we can't get it for > beta 1,have a plan to whitelist it as soon as possible. The Desire is already fixed for beta 2, and will be unblocked when beta 2 is published.
Blocks: 719927
blocking-fennec1.0: --- → ?
per email from akeybl, this needs to be done before today's beta1 launch. Moving to correct component.
Component: General → Release Engineering: Releases
Product: Fennec Native → mozilla.org
QA Contact: general → bhearsum
Version: Trunk → other
Assignee: nobody → aki
Attached image no desire
I don't see the Desire on the list.
(In reply to Aki Sasaki [:aki] from comment #5) > I don't see the Desire on the list. Try seaching for "Desire" -- the list only shows a limited number of results at a time.
(In reply to Matt Brubeck (:mbrubeck) from comment #6) > Try seaching for "Desire" -- the list only shows a limited number of results > at a time. Actually the problem seems to be that only the device name is searched (not the manufacturer), and this device is listed as "Desire" instead of "HTC Desire." I think we want to exclude both "Desire (bravo)" and "Desire (bravoc)" for this release. The Desire S and Desire HD are different models, and they are not necessarily affected by this bug.
Attached image lukas found it
Should we block all of these or a subset?
The Supported Devices page should be updated too: http://www-dev.allizom.org/en-US/mobile/14.0beta/system-requirements/
(In reply to Matt Brubeck (:mbrubeck) from comment #7) > (In reply to Matt Brubeck (:mbrubeck) from comment #6) > > Try seaching for "Desire" -- the list only shows a limited number of results > > at a time. > > Actually the problem seems to be that only the device name is searched (not > the manufacturer), and this device is listed as "Desire" instead of "HTC > Desire." > > I think we want to exclude both "Desire (bravo)" and "Desire (bravoc)" for > this release. The Desire S and Desire HD are different models, and they are > not necessarily affected by this bug. Ok. Done.
(In reply to Kohei Yoshino from comment #9) > The Supported Devices page should be updated too: > http://www-dev.allizom.org/en-US/mobile/14.0beta/system-requirements/ Who will handle this? Other than this I think we're done here.
Attached image excluded devices
(In reply to Kohei Yoshino from comment #9) > The Supported Devices page should be updated too: > http://www-dev.allizom.org/en-US/mobile/14.0beta/system-requirements/ I don't think we need to change this page. Firefox Beta still installs on the Desire, it just won't be updated from XUL to Native until the next beta.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
(In reply to Matt Brubeck (:mbrubeck) from comment #13) > I don't think we need to change this page. Firefox Beta still installs on > the Desire, it just won't be updated from XUL to Native until the next beta. Oops, I was wrong here. Excluding the Desire affects both XUL and Native, so Firefox Beta will *not* install on the Desire. The device list *does* need updating. Sorry for the confusion.
Beta 1 works fine for me as a fresh install of the beta from Google Play.
Assignee: aki → nobody
Component: Release Engineering: Releases → Graphics
Product: mozilla.org → Core
QA Contact: bhearsum → thebes
Version: other → 1.0 Branch
blocking-fennec1.0: ? → beta+
Assignee: nobody → aki
Component: Graphics → Release Engineering: Releases
Product: Core → mozilla.org
QA Contact: thebes → bhearsum
Version: 1.0 Branch → other
Do we need a new bug to reverse this change for Friday?
Blocks: 755894
Filed 755894.
Component: Release Engineering: Releases → Graphics
Product: mozilla.org → Core
Version: other → Trunk
Component: Graphics → Release Engineering: Releases
Product: Core → mozilla.org
Version: Trunk → other
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: