David Tardon wrote > I think explicitly setting a bug to ASSIGNED is pretty much pointless. > You cannot force a developer to start working on a bug just because he > has been assigned to it; on the other side, seeing that a bug is already > assigned might discourage others from taking it.
Couldn't agree more. Here is a perfect example of an ASSIGNED bug which could (probably) already been fixed https://bugs.freedesktop.org/show_bug.cgi?id=38451 -- View this message in context: http://nabble.documentfoundation.org/Re-Bug-Status-NEW-but-Assigned-to-Someone-Please-Change-tp4029440p4029569.html Sent from the QA mailing list archive at Nabble.com. _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: [email protected] Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
