Niko Sams wrote:
Hi,
Hello, more discussion about how to handle bugs are welcome, I
hope. Wasn't
able to get in to the earlier thread, so I thought I should
post something
here.
In short: DrKonqi shouldn't create bugs directly but talk to
a layer
between.
This really depends on how
On Monday 12 March 2012 02:14:00 Teemu Rytilahti wrote:
Niko Sams wrote:
Hi,
Hello, more discussion about how to handle bugs are welcome, I
hope. Wasn't
able to get in to the earlier thread, so I thought I should
post something
here.
In short: DrKonqi shouldn't create bugs directly
On Sunday 11 March 2012 11.26.53 Niko Sams wrote:
I'd like to talk about an idea on how DrKonqi
[]
What software could crashes.kde.org run? I'm not sure, maybe abugzilla
installation or somethingcustom written. Or some other bugtracking software.
I'd say this is a great idea, mostly because
Milian Wolff wrote:
Hi again,
While nice this is not required for Niko's proposal. Either the backtrace
is automatically associated with a solution, or a developer later on
associates it with a solution or a bug report. In the former case, the
user gets direct feedback on what's going on. In
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104149/#review11317
---
Ship it!
Ship It!
- Jeremy Paul Whiting
On March 4, 2012,
On Mon, March 12, 2012 10:36 am, Thomas Zander wrote:
On Sunday 11 March 2012 11.26.53 Niko Sams wrote:
I'd like to talk about an idea on how DrKonqi
[]
What software could crashes.kde.org run? I'm not sure, maybe abugzilla
installation or somethingcustom written. Or some other bugtracking
On Sun, Mar 11, 2012 at 13:57, henry miller h...@millerfarm.com wrote:
Good ideas, if anyone actually implements it. A couple of comments.
Most users are not programmers - they will not know how to recogize similear
backtraces are the same root cause. Worse I know of many cases where I - a
On Mon, Mar 12, 2012 at 19:34, Martin Gräßlin mgraess...@kde.org wrote:
On Monday 12 March 2012 19:26:27 Niko Sams wrote:
On Sun, Mar 11, 2012 at 13:57, henry miller h...@millerfarm.com wrote:
Good ideas, if anyone actually implements it. A couple of comments.
Most users are not
On Monday 12 March 2012 19:39:12 Niko Sams wrote:
On Mon, Mar 12, 2012 at 19:34, Martin Gräßlin mgraess...@kde.org wrote:
On Monday 12 March 2012 19:26:27 Niko Sams wrote:
On Sun, Mar 11, 2012 at 13:57, henry miller h...@millerfarm.com wrote:
Good ideas, if anyone actually implements it. A
On Mon, Mar 12, 2012 at 09:54, Milian Wolff m...@milianw.de wrote:
On Monday 12 March 2012 02:14:00 Teemu Rytilahti wrote:
- When getting duplicate backtraces from users the bug entry
could be
updated automatically with the version the crash happened,
this would in my
opinion be a plus in a
On Mon, Mar 12, 2012 at 01:14, Teemu Rytilahti t...@iki.fi wrote:
This really depends on how it'd be used, but perhaps yeah,
this might be a
good idea indeed. This is something I encountered while
working on a course
paper earlier this semester. Similar systems are up there for
Mozilla
On Mon, Mar 12, 2012 at 17:32, Thomas Zander zan...@kde.org wrote:
On Monday 12 March 2012 16.20.00 David Jarvie wrote:
There would be an advantage in giving instant feedback to the user if
possible, but if that turns out to be impractical, Thomas's suggestion of
using background processing on
On Mon, Mar 12, 2012 at 11:36, Thomas Zander zan...@kde.org wrote:
On Sunday 11 March 2012 11.26.53 Niko Sams wrote:
I'd like to talk about an idea on how DrKonqi
[]
What software could crashes.kde.org run? I'm not sure, maybe abugzilla
installation or somethingcustom written. Or some
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104198/#review11343
---
Ship it!
Ship It!
- John Layt
On March 8, 2012, 11:04
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104243/
---
Review request for kdelibs.
Description
---
KJS/Grammar: Introduce
15 matches
Mail list logo
