Hello all,
does it make sense to include another status for the regression issues
where the problematic commit has been identified ? I'm asking it because
yesterday I spent some time on this task and I could chase down two
regressions, one of them made by a Collabora developer ( I've already sent
Hi Xisco, *,
Xisco Faulí schreef op 5/06/2014 10:32:
does it make sense to include another status for the regression issues
where the problematic commit has been identified ? I'm asking it
because yesterday I spent some time on this task and I could chase
down two regressions, one of them
Hi,
Jay Philips schreef op 5/06/2014 4:45:
I think it might be a good idea to include the following whiteboard
keywords -
HasDebug or HasBacktrace HasStrace - When the bug reporter or
commenter has included the backtrace or strace output, so devs can
easily see this list
I didn't invent it,
HasDebug or HasBacktrace HasStrace - When the bug reporter or
commenter has included the backtrace or strace output, so devs can
easily see this list
Please consolidate on ONE of those before introducing this and viciously kill
the others. have-backtrace looks find to me and is a registered
On Thu, 2014-06-05 at 14:42 +0200, Joren DC wrote:
Hi Xisco, *,
Xisco Faulí schreef op 5/06/2014 10:32:
does it make sense to include another status for the regression issues
where the problematic commit has been identified ? I'm asking it
because yesterday I spent some time on this
Hi Kohei,
Kohei Yoshida schreef op 5/06/2014 15:06:
So, to me personally, this practice of witch-hunting (or
finger-pointing) really bogs me down, especially I receive such notice
hundreds of times during a typical development cycle.
Well, that's at least not what I'm talking about right now.
On Thu, 2014-06-05 at 15:41 +0200, Joren DC wrote:
Hi Kohei,
Kohei Yoshida schreef op 5/06/2014 15:06:
So, to me personally, this practice of witch-hunting (or
finger-pointing) really bogs me down, especially I receive such notice
hundreds of times during a typical development cycle.
Hi,
On Thu, Jun 05, 2014 at 09:06:07AM -0400, Kohei Yoshida wrote:
So, to me personally, this practice of witch-hunting (or
finger-pointing) really bogs me down, especially I receive such notice
hundreds of times during a typical development cycle.
There is no witch-hunting in this and lets
On Thu, 2014-06-05 at 16:07 +0200, Bjoern Michaelsen wrote:
Hi,
On Thu, Jun 05, 2014 at 09:06:07AM -0400, Kohei Yoshida wrote:
So, to me personally, this practice of witch-hunting (or
finger-pointing) really bogs me down, especially I receive such notice
hundreds of times during a
Hey Xisco,
Hello all,
does it make sense to include another status for the regression issues
where the problematic commit has been identified ? I'm asking it
because yesterday I spent some time on this task and I could chase
down two regressions, one of them made by a Collabora developer (
On 06/05/2014 05:36 AM, Joren DC wrote:
Hi,
Jay Philips schreef op 5/06/2014 4:45:
I think it might be a good idea to include the following whiteboard
keywords -
HasDebug or HasBacktrace HasStrace - When the bug reporter or
commenter has included the backtrace or strace output, so devs
Crap I see ;) Thanks - we can talk about consistency between keyword and
whiteboard once we actually get our own instance of bugzilla :)
Best,
Joel
On 06/05/2014 08:29 AM, Joren DC wrote:
Joel Madero schreef op 5/06/2014 17:26:
Ah I didn't see that. We should change it to camel case to be
On 06/05/2014 05:36 AM, Joren DC wrote:
Hi,
Jay Philips schreef op 5/06/2014 4:45:
I think it might be a good idea to include the following whiteboard
keywords -
HasDebug or HasBacktrace HasStrace - When the bug reporter or
commenter has included the backtrace or strace output, so devs
Joel Madero schreef op 5/06/2014 17:26:
Ah I didn't see that. We should change it to camel case to be
consistent. HaveBacktrace. Will include on whiteboard page.
Just to be sure: have-backtrace is a keyword and our key words are not
camel-cased ;-). We may want to consider to make it more
Hi Joren,
Looking over keywords, you are correct that it has 'have-backtrace', it
even has 'want-backtrace', and it also has keywords that arent that
useful in the keyword field like bibisected (used in WhiteBoard),
NEEDINFO (used in status), and notourbug (used in status).
Regards,
Jay Philips
Hi All,
I think it might be a good idea to include the following whiteboard
keywords -
HasDebug or HasBacktrace HasStrace - When the bug reporter or
commenter has included the backtrace or strace output, so devs can
easily see this list
ConfirmedCrashHalt or ConfirmedCrash ConfirmedHalt-
On 06/04/2014 07:45 PM, Jay Philips wrote:
Hi All,
I think it might be a good idea to include the following whiteboard
keywords -
HasDebug or HasBacktrace HasStrace - When the bug reporter or
commenter has included the backtrace or strace output, so devs can
easily see this list
I like
17 matches
Mail list logo
