Re: Intent to update bugs: Non-GeckoView bugs in Firefox for Android

Emma Humphries <[email protected]> Thu, 12 Jul 2018 15:03:52 -0700
Newsgroups gmane.comp.mozilla.firefox.devel,gmane.comp.mozilla.devel.seamonkey
Message-ID <CAL_vYcpStQvjsWQb5ms6SYGm3At70Poxzn8nNvw4zsgNBXLwaQ@mail.gmail.com>
--===============1558829364137010261==
Content-Type: multipart/alternative; boundary="0000000000001f846c0570d48ca4"

--0000000000001f846c0570d48ca4
Content-Type: text/plain; charset="UTF-8"

Hi Dirkjan and Bruno,

"New strategy" was too strong a phrase for me to use. New organization of
how we track bugs for Android applications is better.

GeckoView is becoming the "common core" for Android applications. Mobile
applications like Focus, Klar, and Rocket have their specific code managed
in GitHub.

I'll late Dave Bolter answer your questions about what we are doing with
Firefox for Android going forward. He can speak better to our Android
roadmap.

But think of it like the Core/Firefox distinction on Desktop Firefox. If
it's in the browser window, it's GeckoView. If its in the browser
chrome/menus, it'll be in Firefox for Android, Klar, Focus, or Rocket.

Sincerely,

Emma Humphries
EPM/Bugmaster, Firefox
Mozilla


On Thu, Jul 12, 2018 at 12:38 AM Dirkjan Ochtman <[email protected]> wrote:

> On Thu, Jul 12, 2018 at 1:50 AM Emma Humphries <[email protected]> wrote:
>
>> Since our strategy for mobile is changing, Susheel's team is focusing on
>> a small number of bugs in Firefox for Android which aren't in the GeckoView
>> component.
>>
>
> Can someone point me to a bit more info on what the new strategy entails?
> I haven't seen anything on this list or Planet Mozilla, but if I want to
> get the product/component right in future bugs, it would be helpful to
> understand how things will fit together.
>
> Kind regards,
>
> Dirkjan
>

--0000000000001f846c0570d48ca4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif">Hi Dirkjan and Bruno, <br></div><div class=3D"gmail_def=
ault" style=3D"font-family:arial,helvetica,sans-serif"><br></div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif">&quot;N=
ew strategy&quot; was too strong a phrase for me to use. New organization o=
f how we track bugs for Android applications is better. <br></div><div clas=
s=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><br></=
div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-=
serif">GeckoView is becoming the &quot;common core&quot; for Android applic=
ations. Mobile applications like Focus, Klar, and Rocket have their specifi=
c code managed in GitHub. <br></div><div class=3D"gmail_default" style=3D"f=
ont-family:arial,helvetica,sans-serif"><br></div><div class=3D"gmail_defaul=
t" style=3D"font-family:arial,helvetica,sans-serif">I&#39;ll late Dave Bolt=
er answer your questions about what we are doing with Firefox for Android g=
oing forward. He can speak better to our Android roadmap. <br></div><div cl=
ass=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><br>=
</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,san=
s-serif">But think of it like the Core/Firefox distinction on Desktop Firef=
ox. If it&#39;s in the browser window, it&#39;s GeckoView. If its in the br=
owser chrome/menus, it&#39;ll be in Firefox for Android, Klar, Focus, or Ro=
cket. <br></div><div class=3D"gmail_default" style=3D"font-family:arial,hel=
vetica,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-fam=
ily:arial,helvetica,sans-serif">Sincerely, <br></div><div class=3D"gmail_de=
fault" style=3D"font-family:arial,helvetica,sans-serif"><br></div><div clas=
s=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif">Emma H=
umphries</div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif">EPM/Bugmaster, Firefox</div><div class=3D"gmail_default" s=
tyle=3D"font-family:arial,helvetica,sans-serif">Mozilla<br></div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><br></d=
iv></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Thu, Jul 12, 20=
18 at 12:38 AM Dirkjan Ochtman &lt;<a href=3D"mailto:[email protected]" ta=
rget=3D"_blank">[email protected]</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><div dir=3D"ltr">On Thu, Jul 12, 2018 at 1:50 AM Emma Humphr=
ies &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">emma@mozilla.=
com</a>&gt; wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><div dir=3D"ltr"><div><div>Since
 our strategy for mobile is changing, Susheel&#39;s team is focusing on a=
=20
small number of bugs in Firefox for Android which aren&#39;t in the=20
GeckoView component.=C2=A0</div></div></div></blockquote><div><br></div><di=
v>Can someone point me to a bit more info on what the new strategy entails?=
 I haven&#39;t seen anything on this list or Planet Mozilla, but if I want =
to get the product/component right in future bugs, it would be helpful to u=
nderstand how things will fit together.</div><div><br></div><div>Kind regar=
ds,</div><div><br></div><div>Dirkjan<br></div></div></div>
</blockquote></div>

--0000000000001f846c0570d48ca4--

--===============1558829364137010261==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/firefox-dev

--===============1558829364137010261==--