If it's useful as a data point, in Gecko we used not to care about
non-unified builds. This worked kind of ok, because the file
arrangements were mostly deterministic by directory. However, folks
running with weird build configurations always ended up hitting these
issues (and they might not
Hi Webkit-Dev Team,
We've been working on the Shared Storage API that supports a variety of use
cases that may be impacted by 3rd Party Cookie Deprecation. The idea is to
provide a storage API (named Shared Storage) that is intended to be
unpartitioned. Origins can write to it from their own
> On Jun 2, 2022, at 2:53 PM, Alexey Proskuryakov wrote:
>
>
> It seems like we still need to host watchlist CC service though, to support
> patch workflow - and we'll have separate lists in GitHub and in Bugzilla,
> unless watchlists are reimplemented.
We would still need to host the
> As such, I also think that the non-unified EWS being green should not be a
> blocker to landing a patch. But I think having it there for information will
> help the situation. At minimum, even if every engineer simply ignores the
> non-unified EWS, it also makes it easier for someone trying
> On Jun 3, 2022, at 7:59 AM, Geoffrey Garen wrote:
>
>>> What is the goal of this proposal?
>>
>> The goal is to increase the stability of the build
>
> Is this goal distinct from preventing regressions from landing? If so, how?
>
>> , speed up EWS by preventing regressions from landing
>
Hi webkit-dev,
We're proposing a small additional function to add to the HTML Standard, named
import.meta.resolve(). See the PR [1] and a mini-explainer [2]. Gecko folks
have reviewed the PR and contributed to the discussion, but any thoughts from
WebKit would be very welcome.
We're hoping to
Thanks for gathering this data!
>> What are some notable cases of recent regressions that have landed because
>> of non-use of commit queue and caused serious problems?
>
> Some recent examples of regressions that would have been prevented by
> mandatory commit/merge-queue as proposed:
>
>
If it isn’t it should be considering how many times I’ve had a cq- come from an
AppleWin build that is in no way affected by my patch.
From: Geoffrey Garen via webkit-dev
Sent: Monday, June 6, 2022 10:40 AM
To: Mark Lam
Cc: Darin Adler ; webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev]
> On Jun 6, 2022, at 1:09 PM, Olmstead, Don wrote:
>
> If it isn’t it should be considering how many times I’ve had a cq- come from
> an AppleWin build that is in no way affected by my patch.
Yes, we have a problem with that AppleWin bot, and it’s one that bothers me
quite a bit, but I don’t
9 matches
Mail list logo
