Hi all, I hope you're all enjoying the holiday season!
I've recently seen a number of bug reports in UNCONFIRMED status that should be in NEEDINFO. If you ask the bug reporter for additional information, for repro steps, for an appropriate test document, etc.., please put the bug in NEEDINFO status and leave a brief note telling the reporter what to do after they reply. I often put this info in parens in a new paragraph, like so: (After answering the questions/uploading a test file/etc..., please change the Status back to UNCONFIRMED. Thanks!) If you find a bug report like this, please change the Status and leave a similar comment yourself. As Wikipedia says: Be bold! Properly classifying bug reports can save us a lot of time in QA, letting us focus our time on things like tracking down obscure bugs on LTSP! (Okay, I'm half joking, but does anyone have access to an LTSP setup? https://bugs.freedesktop.org/show_bug.cgi?id=78129) Thanks, --R P.S. 437 is the number :-) -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
