[Libreoffice-qa] pinging old bugs to retest

[Robinson Tryon]

On Wed, Oct 15, 2014 at 10:02 PM, Tommy <barta at quipo.it> wrote:
> Hi QA guys,
> I had this idea and I want to hear what you think about.
> ...
> I think that there should be a consistent number of those who did not
> receive any new comment in the last 6 months.
>
> it happens frequently to me to retest some of those old untouched bugs and
> see that the were reproducible in older branches available at that time
> (i.e. 4.1.x) but now fixed in 4.3.x or 4.4 master, so I label them as
> RESOLVED WORKSFORME and suggest the original reported to upgrade.
>
> so my suggestion is to do a mass ping campaign with bugzilla QA
> administrators tool and send a message like:

Hi Tommy,
I love the idea of following-up on bug reports that have been
untouched for a while! I'm a little wary about any mass-ping campaigns
for a few reasons:
1) I want to make sure that we're not spamming QA/devs who are
unwittingly cc'd on a bug. The devs can get especially cranky :-)
2) It's hard to tell when a bug was "last tested with older than 6
month LibO versions"
3) There are a number of special cases in which a bug is open, and
might require more work than just "please retest"

Perhaps some combination of querying + reviewing the bug report by
hand could work best here?

> see this example:
> https://bugs.freedesktop.org/show_bug.cgi?id=67040
>
> I opened this one in july 2013, last comment was from january 2014 then I
> forgot about it...
>
> after some time I stumbled upon it again and saw that it was fixed somehow
> during development of 4.3.x branch, so I marked this as WORKSFORME

I think that it's okay for us to be a little more aggressive about our
use of RESOLVED WORKSFORME in general. If the user cares enough about
the bug and still finds it to be present in current builds, then they
can open it again.

Tommy: We've got the Seattle LibreFest Bug Bee coming up. My plan is
to focus on UNCONFIRMED bugs, but if you can identify other bugs to
test -- e.g. a set of NEW bugs that are candidates for having been
fixed -- please let me know, and I'll add them to the mix.

Thanks!
--R

-- 
Robinson Tryon
QA Engineer - The Document Foundation
LibreOffice Community Outreach Herald
qubit at libreoffice.org