On 04/27/2015 05:38 PM, Josh Matthews wrote:
> https://github.com/servo/servo/wiki/Meeting-2015-04-27
Here are some details about the situation in Gaia land. We started by
using GitHub issues, but they were lacking features we really needed,
especially tracking dependencies - both between github i
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 t
On Tue, Apr 28, 2015 at 4:52 PM, Boris Zbarsky 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 way to do
I agree that eventually github is going to not be enough for our use cases
-- Bugzilla has tons of useful features that are necessary for working out.
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 b
Le 28/04/2015 06:52, Boris Zbarsky a écrit :
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 ou
On Tue, Apr 28, 2015 at 7:32 PM, Manish Goregaokar
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 that); but for
> now
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
option
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
htt
> 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
> way to do this that I've been able to find.
This is an issue, but
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 d
10 matches
Mail list logo
