On 4/28/15 5:23 AM, David Bruant wrote:
Another possibility is for the reporter to make a PR with the test case.
Just stop. We're talking about making it _easy_ to report issues, yes?
-Boris
___
dev-servo mailing list
dev-servo@lists.mozilla.org
Migration is a one-time thing, but using a bulkier software, (with plenty
of downsides as listed in the notes) when we already have something that
works, for the half-year to a year (even perhaps more) it takes for us to
scale to a point where we actually need isn't one-time and is the worse
On Tue, Apr 28, 2015 at 7:32 PM, Manish Goregaokar manishsm...@gmail.com
wrote:
But I think that as long as the glove still fits, we should use it.
Perhaps reevaluate when we start shipping something (Rust-in-Gecko is
already being
tracked on Bugzilla and we' probably should continue with
On 4/28/15 10:33 AM, Jack Moffitt wrote:
This is an issue, but hasn't hit us much yet.
Sure. I assume if it had you would have been dealing with it. ;)
It's easy enough to use the ``` syntax to include arbitrary things
into a bug report. This is how we often attach logs and such. You
can't
https://github.com/servo/servo/wiki/Meeting-2015-04-27
Cheers,
Josh
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 4/27/15 8:38 PM, Josh Matthews wrote:
https://github.com/servo/servo/wiki/Meeting-2015-04-27
I've mentioned this a few times, but...
For a layout engine, being able to attach an actual testcase to a bug
report is _really_ useful once you get out of just build it mode and
into fix all the
On Tue, Apr 28, 2015 at 4:52 PM, Boris Zbarsky bzbar...@mit.edu wrote:
For a layout engine, being able to attach an actual testcase to a bug
report is _really_ useful once you get out of just build it mode and into
fix all the bugs in this thing you built mode. Github issues simply have
no
7 matches
Mail list logo
