Web lists-archives.com

Re: Bugzilla maintenance work




Hi all,


On Fri, Jun 16, 2017 at 9:59 PM, Christoph Feck <cfeck@xxxxxxx> 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 duplicates, untriaged, etc. How can I go about
>> getting permission to do things like change bug statuses? For example,
>> I'd like to:
>>
>> - Mark https://bugs.kde.org/show_bug.cgi?id=374954 as a duplicate of
>> https://bugs.kde.org/show_bug.cgi?id=375993.
>>
>> - Confirm https://bugs.kde.org/show_bug.cgi?id=381265
>>
>> - Pass back https://bugs.kde.org/show_bug.cgi?id=381269 with NEEDINFO
>
>
> I have given you rights to change all aspects of a bug.
>
> Use wisely.
>
> Note, however, that we use the CONFIRMED state when a developer investigated
> the issue, understands the reason for the bug, and documents it. That's the
> reason a regular user cannot change the status to CONFIRMED. A triager or
> developer (on seeing this state), might assume someone else already
> investigated the issue if it was changed without the proper investigation.
>
> The type of confirmation the user wants to see is simply the fact that the
> bug is open. If it was not a bug to begin with, or was investigated to be
> caused by a bug outside our software, it will be clossed.

Sorry to chime in late, but for completion's sake, please have a look
at our Community wiki for a few guidelines:
https://community.kde.org/Guidelines_and_HOWTOs/Debugging

As a bug triager and non-developer, I only confirm bugs I can
reproduce myself, and which have clear steps on how to reproduce a
bug, and/or have been confirmed by more than one user. Sadly there are
plenty of reports that lack these steps, so most of the time I have to
ask for more information (and set the status to NEEDSINFO, so it is
easy to search) which I investigate on a regular basis and close them
if there is no feedback within a reasonable time (with our fast paced
development, reasonable in my book is not exceeding 6 weeks, taking
into account holiday breaks of the OR). I then close all those still
missing information as invalid with the mention that we gladly reopen
the bug if the missing information is provided.

Nice to have you on board, Nate :-)

Regards, Myriam

-- 
Proud member of the Amarok and KDE Community
Protect your freedom and join the Fellowship of FSFE:
http://www.fsfe.org
Please don't send me proprietary file formats,
use ISO standard ODF instead (ISO/IEC 26300)