[Libreoffice-qa] ping to retest old bugs

bfoman bfo.bugmail at spamgourmet.com
Thu Oct 16 12:00:16 PDT 2014

Tommy wrote
> we currently have 799 UNCONFIRMED and 7793 NEW bugs.
> I think that there should be a consistent number of those who did not  
> receive any new comment in the last 6 months.
> [...]
> meanwhile, so please retest with current LibO release ( and give  
> feedback of the actual status of the bug. if bug is gone set status to  
> RESOLVED WORKSFORME. if bug is still present leave status UNCHANGED and  
> drop a new comment telling the LibO version where you retested and  
> reproduce it

It is tempting to do it every branch (every 6 months), but that could be too
often and annoy people if the bug is still there. Considering current
release schedule for 4.3 and realistic chances for getting fixes I think we
should ask to check the bugs against master and do this ping before hard
code freeze and branching. I noticed that usually serious bugs are fixed in
master or in earlier stages of particular branch, than backported to last
few maintenance releases of the fresh branch. This ping should give the
reporters the true message about current status of the issue and more
testers of the next release. This also perfectly fits planned 4.4 BH
Best regards.

View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-ping-to-retest-old-bugs-tp4125930p4126029.html
Sent from the QA mailing list archive at Nabble.com.

More information about the Libreoffice-qa mailing list