On Wed, 2013-02-13 at 10:59 +0100, Olav Vitters wrote: > On Wed, Feb 13, 2013 at 06:53:17AM +0100, Martin Pitt wrote: > > Travis Reitter [2013-02-12 13:21 -0800]: > > > On Tue, 2013-02-12 at 07:43 +0100, Martin Pitt wrote: > > > > To make this really useful, we can't rely on developers checking this > > > > every hour or every day, of course; instead we need push notifications > > > > as soon as a module starts failing. That's the bit which needs broader > > > > discussion and consent. > > > > > > I'd like to offer: > > > > > > (0) auto-file an urgent/critical bug against the module in the case of > > > build breaks (and maybe high/major for test breaks?) > > > > Claudio Saavedra [2013-02-12 23:24 +0200]: > > > (3) Automatically filing a bug in the broken module with the details of > > > the breakage and additionally CC: whoever might be interested in keeping > > > an eye on the continuous integration? > > > > This creates more overhead, but I like this proposal as well. I guess > > one can use python-bzutils and the like to auto-create bugs, and > > remember on the Jenkins side which bug was opened for which module, > > and auto-close it once the build works again. > > > > The main issue that I see with this is that it's much harder to filter > > away/opt out, so it requires some broader consensus that we want to do > > this. We can still add a module blacklist if needed, though. > > I think build issues should be filed as Bugzilla bugs. At most we maybe > want to set some keyword / status whiteboard. But I guess the summary > would be consistent and people will quickly learn of it.
They should be filed as Bugzilla bugs *after a timeout*. We already see build failures on ostree popping up on the #testable channel, and those are usually fixed in a timely manner. If you file the bugs as soon as they're visible, you'll end up filing outdated bugs, and severely reducing the good will of the people fixing those bugs. I don't think it would personally take me very long to yell "I KNOW" at the bugmail and want to opt-out. Bugmail should be for long-standing issues. If the problem can be solved under 10/15 minutes, don't start nagging people watching the bug mail. _______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
