As brought-up by Bjoern during the meeting, it's good for us if we can identify how many regressions have been introduced during the course of a (minor) release series of LibreOffice.
https://wiki.documentfoundation.org/QA/Meetings/2013/May_3#PENDING_ITEM:_Regressions_within_a_release One good way to tackle this problem would be to bibisect any bug marked as a regression and try to date it to before the X.X.0 point release. Joel - How much work would it be to bibisect the regressions for each release? Aside from initial triage/repro, what other QA tasks should take priority over this work? --R _______________________________________________ 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/
