[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Firefox 52's end of life, packaging Chromium
From: |
Ricardo Wurmus |
Subject: |
Re: Firefox 52's end of life, packaging Chromium |
Date: |
Thu, 30 Aug 2018 14:11:21 +0200 |
User-agent: |
mu4e 1.0; emacs 26.1 |
Hi Clément,
>>> So the question is: can we push the Chromium package? I've read it's
>>> almost ready[2].
>>
>> The TODO list for convenience:
>>
>> --8<---------------cut here---------------start------------->8---
>> * There is still some data transmitted when starting the browser for the
>> first time. It seems related to the "domain_reliability" component.
>> * Remove remaining "Web Store" links. Currently I've only found it in
>> settings, under "accessibility" and "fonts".
>> * Opening settings transmits a bunch of data, the next version will
>> include the 'disable-translation-lang-fetch' patch from Inox.
>> * PDFium is built, but does not seem to work (the 'install' phase
>> probably needs tweaking). Might just disable it instead.
>> --8<---------------cut here---------------end--------------->8---
>>
>> It would be *very* nice if the first and third items could be solved
>> before merging, but I don’t consider them blockers.
>
> It's not clear to me :-) Does it mean we can merge?
I’ll leave that up to Marius, because he is much more familiar with the
patch than I am.
I would not object to merging it, but I’d like to see these TODOs as
separate bug reports, with the first and third items at a higher
severity than “normal”.
--
Ricardo
Re: Firefox 52's end of life, packaging Chromium, Nils Gillmann, 2018/08/30
Re: Firefox 52's end of life, packaging Chromium, Ricardo Wurmus, 2018/08/30
Re: Firefox 52's end of life, packaging Chromium, Ludovic Courtès, 2018/08/30
Re: Firefox 52's end of life, packaging Chromium, Benjamin Slade, 2018/08/31