Hi all,
On Fri, Jun 16, 2017 at 9:59 PM, Christoph Feck wrote:
> Hi Nate,
>
> On 16.06.2017 19:24, Nate Graham wrote:
>>
>> In my past life, I've done a lot of issue tracker and bug management
>> work, and I'd like to do the same for the KDE bugzilla, where there are
>> a lot of bugs that are du
On 06/16/2017 04:34 PM, Nate Graham wrote:
FWIW, I can reproduce it 100% with the following exact sequence of
keypresses:
Alt+space
= key
F key
2 key
[crash]
No backtrace is generated, though, either on the console or via drkonqi.
What could be up with that?
Never mind, I got a backtrace an
On 06/16/2017 02:38 PM, Christoph Feck wrote:
On 16.06.2017 22:28, Nate Graham wrote:
Thank you, Chris.
So I should not mark a bug as CONFIRMED when I or someone else has
simply reproduced it? The most logical meaning to me is that CONFIRMED
means "We've verified that this is a real bug but w
On 16.06.2017 22:28, Nate Graham wrote:
Thank you, Chris.
So I should not mark a bug as CONFIRMED when I or someone else has
simply reproduced it? The most logical meaning to me is that CONFIRMED
means "We've verified that this is a real bug but we don't yet know
what's causing it".
If you can
Nate Graham ha scritto:
> Thank you, Chris.
>
> So I should not mark a bug as CONFIRMED when I or someone else has simply
> reproduced it? The most logical meaning to me is that CONFIRMED means "We've
> verified that this is a real bug but we don't yet know what's causing it".
It depends on the s
Thank you, Chris.
So I should not mark a bug as CONFIRMED when I or someone else has
simply reproduced it? The most logical meaning to me is that CONFIRMED
means "We've verified that this is a real bug but we don't yet know
what's causing it".
Might it make sense to introduce another state (
Hi Nate,
On 16.06.2017 19:24, Nate Graham wrote:
In my past life, I've done a lot of issue tracker and bug management
work, and I'd like to do the same for the KDE bugzilla, where there are
a lot of bugs that are duplicates, untriaged, etc. How can I go about
getting permission to do things like
Hello everyone!
In my past life, I've done a lot of issue tracker and bug management
work, and I'd like to do the same for the KDE bugzilla, where there are
a lot of bugs that are duplicates, untriaged, etc. How can I go about
getting permission to do things like change bug statuses? For examp
