jmadero wrote > I'm curious if anyone has any thoughts about bugs that have backtraces > but QA has been unable to repro. Should these just be pushed to NEW ?
I think so. It was the accepted procedure for this bug https://bugs.documentfoundation.org/show_bug.cgi?id=62381 If there is a backtrace it is a proven bug even if the people in QA can not reproduce it (either because they don't use the same programs, they aren't on the same locale, etc) If it is set to New, then some developer might be interested in fixing it. If s/he needs further information then it can only be provided by the OP, not by QA. Just my 2 cents. -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-Bugs-with-Backtrace-but-Not-Reproduced-tp4142359p4142374.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/
