Re: Coding style 🙄 : `int` vs `intX_t` vs `unsigned/uintX_t`

2019-07-08 Thread Gerald Squelart
Thank you all for some very interesting discussions so far. Even if we don't take blanket steps to avoid unsigned types in non-bitfield/modulo cases (as suggested by our newly-adopted Google style), at least hopefully we're now aware of their subtleties, and we can be more careful and deliberat

Intent to unship: 3-valued position syntax from , ,

2019-07-08 Thread Boris Chiou
Hi, The spec for only accepts 1,2, or 4-valued syntax. so I'd like to retire the 3-valued positions from these CSS properties (i.e. , , and ). Blink retired this support in Chrome 68, and we are planning to retire them to match the spec, t

Re: Intent to Implement: CSS backdrop-filter

2019-07-08 Thread Connor Brewster
Hi Ehsan, Currently, the plan is to develop this feature behind a pref flag that will be off by default. We haven't decided the best way forward for enabling this feature by default yet. We have two possible options: 1. Add backdrop filter support to the other render backends. 2. Rely on an @sup

Re: Inbound change to Are We Triaged Yet?

2019-07-08 Thread Emma Humphries
To clarify, these reports are defects only: * Untriaged defects with needinfos pending * Untriaged defects without needinfos Remember it's a triage power-move to look at bug descriptions and move them to enhancements or tasks if they aren't bugs. -- Emma On Mon, Jul 8, 2019 at 2:05 PM Emma Hump

Re: Changes to “ExposureGuidelines” (Intent to *)

2019-07-08 Thread Ehsan Akhgari
On Sat, Jul 6, 2019 at 1:56 AM Anne van Kesteren wrote: > On Sat, Jul 6, 2019 at 2:44 AM Ehsan Akhgari > wrote: > > Does the page need to include some of this description? > > It has this: > > # It's acceptable to merge the "intent to prototype" into the > # "intent to ship" email as long as all

Re: Soft Code Freeze for Firefox 69 starts July 1st

2019-07-08 Thread Ryan VanderMeulen
The Gecko version on mozilla-central has now been bumped to 70 and with that, the soft freeze is over. Thanks, Ryan On Tue, Jun 25, 2019 at 1:37 PM Pascal Chevrel wrote: > Hi all, > > On July 1st, we will be merging Firefox 69 from mozilla-central to beta > for the first time. In order to avoid

Inbound change to Are We Triaged Yet?

2019-07-08 Thread Emma Humphries
Hello, With today's merge for Firefox 70, I'm pushing a small, but hopefully useful change to our triage dashboards at https://are-we-triaged-yet.herokuapp.com/. I'm breaking out untriaged bugs into two groups: * Untriaged bugs with needinfos pending * Untriaged bugs without needinfos I'm doing

Re: Revising the frequency threshold for disabling intermittents?

2019-07-08 Thread Gijs Kruitbosch
On 08/07/2019 18:29, Maher( 馬羅成 )Joel wrote: Getting accurate data on this is hard as we do a great job of tracking all failures, but not all passing instances. How hard would it be to fix this? Is it tracked / part of some team's work at the moment? ~ Gijs __

Re: Revising the frequency threshold for disabling intermittents?

2019-07-08 Thread Botond Ballo
On Mon, Jul 8, 2019 at 1:29 PM Maher( 馬羅成 )Joel wrote: > Here you can see the pushes we have over time: > https://sql.telemetry.mozilla.org/dashboard/firefox-ci > > looking at a monthly level, I see these numbers for (autoland, inbound, > central): > July 2018 - 2049 > June 2019 - 2376 Ok, I gue

Re: Revising the frequency threshold for disabling intermittents?

2019-07-08 Thread Maher( 馬羅成 )Joel
Thanks for bringing this topic up Botond. The total pushes includes try as well, so that is slightly misleading. We do not add annotations from try typically (there are some cases where that is done, but not the standard role of the sheriffs). Here you can see the pushes we have over time: https

Revising the frequency threshold for disabling intermittents?

2019-07-08 Thread Botond Ballo
Hi folks, We have a policy of disabling intermittently failing tests is they fail more than 150 times over 21 days [1] (revised from 200 times over 30 days [2], which was a very similar failure rate just evaluated over a slightly longer period). When the policy was originally put in place in Sept

Intent to prototype and ship: CSS `quotes: auto`

2019-07-08 Thread Jonathan Kew
Summary: Adding a new `auto` value as the initial value of CSS `quotes` property, with the behavior that language-sensitive quotation marks (derived from CLDR) are used for quote-open/close generated content. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1421938 Standard: https://drafts.c

Re: Update: m-c is now reformatted, trees will reopen shortly

2019-07-08 Thread Victor Porof
Hey Marco, The whitespace changes are expected; there are no other parts which await landing. Readability might be better or similar as before, depending on the original code. And having more consistency and predictability, not just within teams but within Mozilla, is a good thing. This reduce

[desktop] Bugs logged by Desktop Release QA in the last 7 days

2019-07-08 Thread Mihai Boldan
Hello, Here's the list of new issues found and filed by the Desktop Release QA team in the last 7 days. Additional details on the team's priorities last week, as well as the plans for the current week are available at: https://tinyurl.com/yy94plhc. Bugs logged by Desktop Release QA in the last