Re: Rust and --enable-shared-js

2018-10-03 Thread Mike Hommey
On Tue, Oct 02, 2018 at 03:25:04PM +0300, Henri Sivonen wrote: > On Mon, Sep 24, 2018 at 3:24 PM, Boris Zbarsky wrote: > > On 9/24/18 4:04 AM, Henri Sivonen wrote: > >> > >> How important is --enable-shared-js? I gather its use case is making > >> builds faster for SpiderMonkey developers. > > > >

Subject: NodeJS now a hard requirement for building Firefox

2018-10-03 Thread dmose2
As previously announced[1], Firefox builds now (or momentarily will) have a hard-dependency on NodeJS 8.11.0 or newer. Anyone (other than certain specific automation tasks) who has been using --disable-nodejs in their mozconfig as a workaround for problems should now remove this in order for th

Re: Any plans to move the bug re. low cipher strength in Firefox' master password forward one day?

2018-10-03 Thread Justin Dolske
Yes, we're looking at it, but don't have a detailed plan or schedule to share yet. Justin On Wed, Oct 3, 2018 at 10:40 AM Jörg Knobloch wrote: > Hi all, > > an unrelated discussion made me aware that the master password cipher > strength bug[1] is still open. Any plans to tackle that? > > Other

Any plans to move the bug re. low cipher strength in Firefox' master password forward one day?

2018-10-03 Thread Jörg Knobloch
Hi all, an unrelated discussion made me aware that the master password cipher strength bug[1] is still open. Any plans to tackle that? Other software uses strong AES algorithms for their "password collections". Would it be hard to follow? Jörg. [1] https://bugzilla.mozilla.org/show_bug.cgi

PSA: Dangling Commas landing part 2 - 20th Oct

2018-10-03 Thread Mark Banner
Following the successful enabling of the ESLint comma-dangle rule for some of our javascript files, I am intending on enabling it for the rest on Friday 20th October. This is at the end of the soft freeze period, but just before the merges happen, to make uplifts easier. This will affect any

Re: Multi-browser web-platform-tests results dashboard

2018-10-03 Thread James Graham
On 03/10/2018 13:32, Boris Zbarsky wrote: On 10/3/18 5:21 AM, James Graham wrote: So the net effect of all this is that bug fixes won't appear on the dashboard until the first upstream wpt commit after they are present in a nightly release. Right. I assume for now the volume of commits to wp

Re: Multi-browser web-platform-tests results dashboard

2018-10-03 Thread Boris Zbarsky
On 10/3/18 5:21 AM, James Graham wrote: Commits to mozilla repos aren't involved Right, that's what I was assuming. So the net effect of all this is that bug fixes won't appear on the dashboard until the first upstream wpt commit after they are present in a nightly release. Right. I assum

Re: Multi-browser web-platform-tests results dashboard

2018-10-03 Thread James Graham
On 02/10/2018 21:27, Boris Zbarsky wrote: On 10/2/18 1:38 PM, James Graham wrote: Experimental (i.e. nightly/dev) builds of Firefox and Chrome are run on Linux using Taskcluster after each commit to web-platform-tests. Would a commit to Firefox that fixes some tests and just touches wpt .ini