How to mark bugs - was - Re: Some interesting info while researching mkisofs

[Jeremy Whiting]

I thought we would just add a comment to the bug itself (and maybe
mark it as confirmed, or assigned etc.)



On Fri, Sep 26, 2014 at 4:59 PM, Albert Astals Cid <aacid at kde.org> wrote:
> El Divendres, 26 de setembre de 2014, a les 12:22:51, Scarlett Clark va
> escriure:
>> On Friday, September 26, 2014 12:57:52 PM Jeremy Whiting wrote:
>> > My first thought for going through the list in a distributed manner is
>> > to use the list itself? Maybe we could filter on last comment, and as
>> > we investigate each one, leave a comment in the bug itself saying what
>> > we think of it? If we want to keep the investigation separate from the
>> > bugs themselves (to not generate a bunch of bugzilla e-mails or
>> > something) notes.kde.org would work with bug numbers and such.
>>
>> I think we should go through the actual bugs, so we all know what bugs have
>> what progress and not repeating effort. Plus it shows activity to the users.
>> Scarlett
>
> But how do we mark bugs?
>
> e.g. https://bugs.kde.org/show_bug.cgi?id=337428 seems like it would one of
> the "easy ones" to fix, where do i had it? the kanboard?
>
> Cheers,
>   Albert
> _______________________________________________
> Kde-gardening mailing list
> Kde-gardening at kde.org
> https://mail.kde.org/mailman/listinfo/kde-gardening