Re: bugs.maemo.org and moving bugs from UNCONFIRMED to NEW
Hi, Am Sonntag, den 03.05.2009, 10:38 -0400 schrieb Anderson Lizardo: I can't find anything about this on the maemo Wiki (http://wiki.maemo.org/Bugs:Triage_guide did not help, and a search for bugzilla on the wiki neither), therefore I ask here: How is a bug stated as UNCONFIRMED moved to NEW? It seems that having a bug assigned to me is not enough to allow me marking it as NEW or even change to this status automatically (as it is done in most bugzilla systems I've used). You need canconfirm permissions to move a bug from UNCOMFIRMED to NEW state. Other option: 3 persons voting for a specific UNCONFIRMED bug report will also automatically confirm the bug and change it to NEW. The wikipage mentioned to ask the Bugsquad members to provide editbugs permissions to you so you have gain much more power to change things and work efficiently. I've added more information about UNCONFIRMED-NEW; I hope it's clearer now. andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: bugs.maemo.org and moving bugs from UNCONFIRMED to NEW
On Mon, May 4, 2009 at 11:05 AM, Anderson Lizardo anderson.liza...@openbossa.org wrote: I think it would also be nice to fix the text in https://bugs.maemo.org/page.cgi?id=fields.html#status too (it is the page that's shown when you click on the Status link in the bug report page), as it says: UNCONFIRMED This bug has recently been added to the database. Nobody has validated that this bug is true. Users who have the canconfirm permission set may confirm this bug, changing its state to NEW. Or, it may be directly resolved and marked RESOLVED. Should it be editbugs instead of canconfim ? Ok, I just saw on the Triage Guide (with your changes) that the above is correct. Sorry about the confusion :/ Regards, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: bugs.maemo.org and moving bugs from UNCONFIRMED to NEW
On Mon, May 4, 2009 at 4:37 AM, Andre Klapper aklap...@openismus.com wrote: You need canconfirm permissions to move a bug from UNCOMFIRMED to NEW state. Other option: 3 persons voting for a specific UNCONFIRMED bug report will also automatically confirm the bug and change it to NEW. Ok, that's clear now. The bug in case was one that the developer (myself) detected and fixed even before somone voted on it. The wikipage mentioned to ask the Bugsquad members to provide editbugs permissions to you so you have gain much more power to change things and work efficiently. Well, even though I saw this note, I didn't really understand exactly what editbugs permissions would give me, because I don't have these permissions :). I've added more information about UNCONFIRMED-NEW; I hope it's clearer now. I think it would also be nice to fix the text in https://bugs.maemo.org/page.cgi?id=fields.html#status too (it is the page that's shown when you click on the Status link in the bug report page), as it says: UNCONFIRMED This bug has recently been added to the database. Nobody has validated that this bug is true. Users who have the canconfirm permission set may confirm this bug, changing its state to NEW. Or, it may be directly resolved and marked RESOLVED. Should it be editbugs instead of canconfim ? Regards, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
