From: Gary Thomas <gary@mlbassoc.com>
To: toaster@yoctoproject.org
Subject: Re: Reference browser for testing purposes
Date: Fri, 28 Mar 2014 12:56:03 -0600 [thread overview]
Message-ID: <5335C5C3.80009@mlbassoc.com> (raw)
In-Reply-To: <2161222.Ta40XWiXqk@peggleto-mobl5.ger.corp.intel.com>
On 2014-03-28 12:41, Paul Eggleton wrote:
> On Friday 28 March 2014 12:12:22 Barros Pena, Belen wrote:
>>>> On Wed, Mar 19, 2014 at 4:23 PM, Barros Pena, Belen
>>>> <belen.barros.pena@intel.com> wrote:
>>>>
>>>> We should probably have raised this question earlier and had a plan in
>>>> place, but hey, better late ... The question is: which browsers should we
>>>> be using as a reference for QA purposes? Our guideline here is decent
>>>> HTML5 compatibility, but we never qualified what 'decent' means.
>>>>
>>>> The other reference we could use is traffic to the Yocto Project website.
>>>> Visits are mainly coming from Chrome 32 and 33 on Windows, and Firefox 26
>>>> and 27 on Linux. I can put together more detailed numbers if anybody
>>>> wants to see them.
>>>>
>>>> Those might be a bit too cutting edge, but could guide our decision
>>>> somehow. QA is currently testing with Firefox 11: that is probably too
>>>> old.
>>>>
>>>> In light of the above, any suggestions about which browsers we should use
>>>> for testing?
>>
>> Just in case is useful, a list of the supported distros and their browsers
>> (the ones I could find):
>>
>> * Ubuntu 12.04 (LTS) - Firefox 11.0
Ubuntu 12.04 is actually on Firefox 28.0 (normal fully updated system)
You also don't seem to have much representation of Google Chrome which
is one of the more common optional browsers, currently at 33.0.1750.152
Even if 12.04 is LTS, some things _are_ kept fairly current :-)
>>
>> * Ubuntu 12.10 - Firefox 16.0.1
>>
>> * Ubuntu 13.04 - Firefox 20.0
>
> We'll need to add Ubuntu 13.10 here, and probably drop Ubuntu 12.10
>
>> * Fedora release 18 (Spherical Cow) - Firefox 17.01
>
> Fedora 18 is out of support so we'll be dropping it for 1.6.
>
>> * Fedora release 19 (Schrödinger's Cat) - Firefox 21.0
>
> We'll need to add Fedora 20 (Firefox 28.0 here).
>
>> * CentOS release 6.4 - ?
>>
>> * Debian GNU/Linux 6.0.7 (Squeeze) - ?
>
> I wouldn't bother with these two to be honest.
>
>> * Debian GNU/Linux 7.0 (Wheezy) - Chromium 26.0.1410.43 and Firefox 10.0.12
>>
>> * Debian GNU/Linux 7.1 (Wheezy) - ?
>>
>> * openSUSE 12.2 - Firefox 14.0.1
>
> Drop openSUSE 12.2, we should be dropping it from our support list
>
>> * openSUSE 12.3 - Firefox 19.0
>
> We probably want openSUSE 13.1 as well.
>
> (FWIW I've just sent a note to QA to get our tested distro list updated.)
>
> Cheers,
> Paul
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-03-28 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 12:12 Reference browser for testing purposes Barros Pena, Belen
2014-03-28 18:41 ` Paul Eggleton
2014-03-28 18:56 ` Gary Thomas [this message]
2014-03-31 8:28 ` Barros Pena, Belen
-- strict thread matches above, loose matches on Subject: below --
2014-03-19 16:23 Barros Pena, Belen
2014-03-19 17:21 ` Georgescu, Alexandru C
2014-03-19 18:14 ` Damian, Alexandru
2014-03-20 3:38 ` Yuan Sun
2014-03-20 11:09 ` Barros Pena, Belen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5335C5C3.80009@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=toaster@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.