[dev-servo] Meeting notes 4/27 (Reviewable; blog posts; github/BMO; infra issues; Whistler planning)
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
Re: [dev-servo] Meeting notes 4/27 (Reviewable; blog posts; github/BMO; infra issues; Whistler planning)
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 issues and between gaia and gecko. Github issues really scaled poorly for b2g QA needs, but the situation may be totally different for servo indeed. So at some point we moved all the open GitHub issues to bugzilla. This was not pretty ;) For releng purposes, we also needed a more flexible and powerful system of tags and flags than the labels. Here again, b2g has to track different branches with their gecko counterpart, etc. which you probably don't need (yet). About the workflow, it's true that attaching links to PR in bugzilla was a bit awkward, but we now have an autolander system that works mostly automagically if the bug number is part of the PR title. So I would call that problem solved. Fabrice -- Fabrice Desré b2g team Mozilla Corporation ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
Re: [dev-servo] Meeting notes 4/27 (Reviewable; blog posts; github/BMO; infra issues; Whistler planning)
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 bugs in this thing you built" mode. Github issues simply have no way to do this that I've been able to find. You can put testcases on jsfiddle or other such services, but it's really hard to do minimal testcases that way because of all the things those services pull in, it's impossible to test some things (e.g. parser issues, quirks mode) because there's little control over the markup, and there are absolutely no guarantees your testcase will be around in 5 years when you want to see what that code change was trying to fix. This is really a problem I expect you'll want to solve at some point if you want to be able to get useful functionality bug reports and community QA. -Boris ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
Re: [dev-servo] Meeting notes 4/27 (Reviewable; blog posts; github/BMO; infra issues; Whistler planning)
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 this that I've been able to find. You can put testcases on > jsfiddle or other such services, but it's really hard to do minimal > testcases that way because of all the things those services pull in, it's > impossible to test some things (e.g. parser issues, quirks mode) because > there's little control over the markup, and there are absolutely no > guarantees your testcase will be around in 5 years when you want to see > what that code change was trying to fix. > > This is really a problem I expect you'll want to solve at some point if > you want to be able to get useful functionality bug reports and community > QA. Developers can commit testcases to a github repo and reference them with github.io URLs, but that's no good for casual (e.g. web-developer level) bug reporters. So, yes indeed. Rob -- oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo owohooo osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o oioso oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo owohooo osoaoyoso,o o‘oYooouo ofolo!o’o owoiololo oboeo oiono odoaonogoeoro ooofo otohoeo ofoioroeo ooofo ohoeololo. ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
