776101 - Add ARMv6 and x86 build download links to /firefox/channel/#aurora

Status: RESOLVED FIXED

Description

[Lukas Blakk [:lsblakk] use ?needinfo]

Jaclyn, when might we be able to add a download link to the ARMv6 builds to http://www.mozilla.org/en-US/firefox/channel/#aurora ?

The link should point to https://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-aurora-android-armv6/fennec-16.0a2.en-US.android-arm-armv6.apk

Comment 1

[Jaclyn Fu]

+cmore to help us out

Comment 2

[Lukas Blakk [:lsblakk] use ?needinfo]

To be clear, this shouldn't be enabled without checking with Release Management first to make sure we're officially releasing this.  I just need to know how long until the work could be done to have this ready.  Thank you.

Comment 3

[Robert Kaiser]

I also just wondered how stable we think those are already and if we find them release-worthy to the Aurora audience. If so, that would indeed be a great and welcome step! :)

Comment 4

[Chris More [:cmore]]

Lukas: What is the status of this? Since you are in Release Management, we could do this after you give us a date that it could be released. We do weekly releases, but we plan our work in bi-weekly sprints.

Were you thinking about just changing the logic of the Android button so it serves up either the ARMv6 or arm versions automatically based on user agent sniffing?

Comment 5

[Alex Keybl [:akeybl]]

(In reply to Chris More [:cmore] from comment #4)
> Were you thinking about just changing the logic of the Android button so it
> serves up either the ARMv6 or arm versions automatically based on user agent
> sniffing?

I don't believe most Android user agents (outside of Fennec) have actually ever provided platform architecture (see [1]). The easiest thing would be to instead have 2 APK downloads a la [2]. 

[1] http://www.useragentstring.com/pages/Mobile%20Browserlist/
[2] https://nightly.mozilla.org/

Comment 6

[Chris More [:cmore]]

Lukas: How do thinks look on your end to add a link to the ARMv6 build?

I wonder if it would be easier to just have something linked off of this page since that is where all other system links are at:

http://www.mozilla.org/en-US/firefox/all.html

Adding links to the /firefox/channel/#aurora page would require adjusting the design of the page to accommodate these links and it may not really look right with the existing green buttons.

Comment 7

[Lukas Blakk [:lsblakk] use ?needinfo]

We need different styles of buttons to reflect the availability of a second Android download option in different templates since we have two download pages for each channel:


Aurora

http://www.mozilla.org/en-US/firefox/channel/#aurora
http://www.mozilla.org/en-US/mobile/aurora/


Beta:

http://www.mozilla.org/en-US/mobile/beta/
http://www.mozilla.org/en-US/firefox/channel/#beta

In terms of a timeline, we have ARMv6 builds for both channels now that can be made available to download so getting template changes done and signed off should happen right away so we can push the page changes live when we push 16.0b1 (Thursday) and unthrottle Aurora updates (Friday).

Comment 8

[Lukas Blakk [:lsblakk] use ?needinfo]

update: this is going to be pushed to beta 2, so the aurora pages should take priority (by Friday would be best) and then the beta pages ready by next Thursday 9/6.

Comment 9

[Chris More [:cmore]]

Can we proceed to get these buttons changes up on Mozilla.org? This is less of a technical issue and more of a UX one given that we would need two buttons to give the user a choice between platforms.

Comment 10

[Chris More [:cmore]]

(In reply to Lukas Blakk [:lsblakk] from comment #8)
> update: this is going to be pushed to beta 2, so the aurora pages should
> take priority (by Friday would be best) and then the beta pages ready by
> next Thursday 9/6.

Lukas: How big of a priority is this to do on the the Aurora page? P1, P2, or P3? Is there a specific date this should be done?

Comment 11

[Alex Keybl [:akeybl]]

(In reply to Chris More [:cmore] from comment #10)
> (In reply to Lukas Blakk [:lsblakk] from comment #8)
> > update: this is going to be pushed to beta 2, so the aurora pages should
> > take priority (by Friday would be best) and then the beta pages ready by
> > next Thursday 9/6.
> 
> Lukas: How big of a priority is this to do on the the Aurora page? P1, P2,
> or P3? Is there a specific date this should be done?

It's a matter of consistency, as Nightly has a link and the Beta Play Store page serves both ARMv6/7. I'd say this is a P2, since it's difficult to point users at the Aurora ARMv6 download. May go up to a P1 soon as we make more Aurora-specific ARMv6 changes that we need to communicate to testers.

Comment 12

[Holly Habstritt Gaal [:Habber]]

We are making a few updates to the Aurora download page this quarter. 

Are there any updates regarding the comments in this bug, or can I use them as reference when updating this page?

Comment 13

[Sam Mott]

Question: Why do we need a second button? In the GPS we have a single sdk, and that andles both armv6 and armv7 correct? Do we need an additional "armv6" button only!

Comment 14

[Brad Lassey [:blassey] (use needinfo?)]

(In reply to Sam Mott from comment #13)
> Question: Why do we need a second button? In the GPS we have a single sdk,
In google play we have 2 APKs, but the store serves the right one to the device
> and that andles both armv6 and armv7 correct? Do we need an additional
> "armv6" button only!
It may be possible to use UA sniffing to figure out if the user is on an ARMv6 or ARMv7 device and hide the other button. But we'll need to fall back to having 2 buttons if the user comes to the page using a desktop browser or if we can't detect the right version.

Comment 15

[Chris More [:cmore]]

(In reply to Holly Habstritt [:Habber] from comment #12)
> We are making a few updates to the Aurora download page this quarter. 
> 
> Are there any updates regarding the comments in this bug, or can I use them
> as reference when updating this page?

If we are going to be touching the Aurora page, we should make sure it includes the ARMv6 downloads. Are we going to keep it in php or move it to bedrock?

Comment 16

[Holly Habstritt Gaal [:Habber]]

cmore, as far as I know we are keeping it where it is since this is supposed to be a quick update, but I need to talk with the developer for the Aurora updates before I confirm that. It would be ideal to move it to bedrock as long as we are making changes, but this project was a last minute request, so we are going to do what we can before the end of the quarter.

Bug reference for Aurora updates: https://bugzilla.mozilla.org/show_bug.cgi?id=807781

Comment 17

[Jennifer Bertsch [:jbertsch]]

I'd like to pick this back up in February 2013 along with 807781

Comment 19

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

AFAIK, ARMv6 users now can download Firefox from Google Play, so we no longer need a direct link to the APK file.

Comment 20

[Robert Kaiser]

(In reply to Kohei Yoshino [:kohei] from comment #19)
> AFAIK, ARMv6 users now can download Firefox from Google Play

Not for Aurora.

Comment 21

[Aaron Train [:aaronmt]]

Side note; this would also be needed for x86 builds at the same time.

Comment 22

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

Oh, I see... I'll take a look.

Comment 23

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

The download button code is messy... The simplest solution would be like this (sniffing both navigator.platform and navigator.userAgent) but we have to add a noscript support and eventually refactor the code.

>    if (navigator.platform.indexOf('armv6l') !== -1 ||
>            navigator.userAgent.indexOf('armv6l') !== -1) {
>        $('.download-link[href$=".apk"]').attr('href', function(i, val) {
>            return val.replace('android-arm', 'android-arm-armv6')
>                      .replace('aurora-android', 'aurora-android-armv6');
>        });
>    }

Comment 24

[Robert Kaiser]

Well, that is if a browser even sends the architecture in the UA string. If the user is going there on Firefox (say, they have release or beta and want to try Aurora, or they have Nightly and want to move to the more stable Aurora), then we don't see the architecture at all.
We still want to offer ARMv6 and x86 Aurora for those people in some way.

Comment 25

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

navigator.userAgent won't tell us about the platform but
navigator.platform will usually be "Linux armv6l" on ARMv6 devices?

Comment 26

[Robert Kaiser]

(In reply to Kohei Yoshino [:kohei] from comment #25)
> navigator.userAgent won't tell us about the platform but
> navigator.platform will usually be "Linux armv6l" on ARMv6 devices?

Ah, right, that's possible, I tend to forget that nowadays those properties still exist and have values while they're not 1:1 represented in the UA any more.

Comment 28

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

I'm working on this.

Comment 29

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

Created attachment 8357514 [details] [review]
Pull Request on GitHub

Comment 30

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

Created attachment 8358031 [details]
screenshot

Here's a screenshot.

* non-Android platform
* Android default (ARMv7)
* Android (ARMv6)
* Android (x86)

Comment 31

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

Note that this Channel page is not responsive yet, so it looks the same on Android phone and tablet, except the download buttons.

Comment 32

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

There's a JavaScript user agent check to show/hide elements. Can someone test it with one of the physical ARMv6 devices listed here? https://wiki.mozilla.org/index.php?title=Mobile/Platforms/Android&oldid=504407

Comment 33

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

retornam: your WebQA team has any ARMv6 or x86 devices for testing?

Comment 34

[raymond [:retornam] (inactive)]

(In reply to Kohei Yoshino [:kohei] from comment #33)
> retornam: your WebQA team has any ARMv6 or x86 devices for testing?

We don't have any ARM6 devices. I'll ask the Mobile QA team if they have any.

Comment 35

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

Thanks :retornam!

Comment 36

[Gian-Carlo Pascutto [:gcp]]

Do you still need a device? Can someone test this for you? This is somewhat problematic for x86 devices.

Comment 37

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

(In reply to Gian-Carlo Pascutto [:gcp] from comment #36)
> Do you still need a device? Can someone test this for you? This is somewhat
> problematic for x86 devices.

I have already tested this on an x86 build on my Intel-based Galaxy Tab 3. It worked well. Still needs an ARMv6 device for test.

Comment 38

[Gian-Carlo Pascutto [:gcp]]

Can someone with an ARMv6 device test this for you then? What needs to happen to close this bug?

Comment 39

[Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat)]

Ah, I have already tested with the ARMv6 user agent string too. So yes, my pull request is ready. I'll ask someone for review.
https://github.com/mozilla/bedrock/pull/1572#issuecomment-39487227

Comment 40

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/dea93b77213f5c51ea23d8133cd28ac9bcaa3bbb
Fix Bug 776101 - Add ARMv6 and x86 build download links to /firefox/channel/#aurora

https://github.com/mozilla/bedrock/commit/b5c80ba16566b36e1787fb428d3194bb070859f6
Merge pull request #1572 from kyoshino/bug-776101-aurora-armv6

Fix Bug 776101 - Add ARMv6 and x86 build download links to /firefox/channel/#aurora