On 12/02/2018 20:08, smaug wrote:
On 02/09/2018 10:39 PM, James Graham wrote:
On 09/02/2018 19:59, Josh Bowman-Matthews wrote:
On 2/9/18 1:26 PM, James Graham wrote:
* One bug per PR we downstream, filed in a component determined by
the files changed in the PR.
What does this mean exactly? W
On 02/09/2018 10:39 PM, James Graham wrote:
On 09/02/2018 19:59, Josh Bowman-Matthews wrote:
On 2/9/18 1:26 PM, James Graham wrote:
* One bug per PR we downstream, filed in a component determined by the files
changed in the PR.
What does this mean exactly? What is the desired outcome of thes
On 09/02/2018 19:59, Josh Bowman-Matthews wrote:
On 2/9/18 1:26 PM, James Graham wrote:
* One bug per PR we downstream, filed in a component determined by the
files changed in the PR.
What does this mean exactly? What is the desired outcome of these bugs?
They're tracking the process and wil
On 2/9/18 1:26 PM, James Graham wrote:
* One bug per PR we downstream, filed in a component determined by the
files changed in the PR.
What does this mean exactly? What is the desired outcome of these bugs?
Cheers,
Josh
___
dev-platform mailing list
On 2/9/18 1:26 PM, James Graham wrote:
The new code is intended to provide the following improvements over the
old periodic batch sync approach:
Thank you. This is awesome.
-Boris
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://
The new sync for web-platform-tests is now running experimentally. This
provides two way sync between the w3c/web-platform-tests repository on
GitHub and mozilla-central, so allowing gecko developers to contribute
to web-platform-tests using their normal gecko workflow, and ensuring
that we get
6 matches
Mail list logo
