[Mageia-bugsquad] [Bug 41] [WISH] Make the cauldron animated & let it progressively start to boil, cook & then just ooooze when you're finished

Remco Rijnders remco at webconquest.com
Tue Oct 4 12:38:55 CEST 2011


On Tue, Oct 04, 2011 at 09:31:59AM +0000, Marja wrote in 
<20111004093200.6C90A4462B at alamut.mageia.org>:
>
>--- Comment #6 from Marja van Waes <m.van.waes at xs4all.nl> 2011-10-04 13:31:59 CEST ---
>(In reply to comment #4)
>> Really? That's what the triage guide says?
>>
>
>I never saw anything in the Triage guide about what the "assigned" status means
>or about who is supposed to set it to that status, and I still don't see it. I
>don't know whether that is because my brain fools me, or because it really
>isn't there.
>
>
>> I thought only the Assignee sets status to ASSIGNED to show that they are
>> actually working on the bug.
>
>
>I understood the same from D. Morgan, I'll revert the status to "new".
>
>It is confusing, though, status "ASSIGNED" really meaning "WORKING ON SOLUTION"

Taking this to the list and out of the bugreport where this discussion 
doesn't really belong...

I agree that it currently is unclear what this status means. So, at the 
very least we need to address this in the revised triage guide.

To me it seems logical that when something is assigned to a maintainer, 
that that also turns the status to ASSIGNED. If that's not what it means, 
then perhaps the status needs to be changed to better reflect the meaning 
of the status. I don't know what a good alternative would be though... 
"ACCEPTED_BY_MAINTAINER"? "IN_PROGRESS"?

Or should we just leave it at "TRIAGED" and then let the maintainer change 
it to "ASSIGNED"?

Remco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: </pipermail/mageia-bugsquad/attachments/20111004/95d92b2c/attachment.asc>


More information about the Mageia-bugsquad mailing list