[Libreoffice-qa] ping to retest old bugs

[Tommy]

On Thu, 16 Oct 2014 21:00:16 +0200, bfoman <bfo.bugmail at spamgourmet.com>  
wrote:

> 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 (4.3.2.2) 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
>
> Hi!
> 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.

yes, I agree we could do this only for 1 year old bugs if 6 months is too  
often.

> 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.

could be an intelligent thing to do.

> 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
> session.
> Best regards.