Re: [qa-dev] About unconfirmed issues.

[Clytie Siddall]

Reply below...

On 02/07/2008, at 8:23 AM, Badral Sanligiin wrote:

Hi all,
I think, "last in first out" principle might be better for the issue

and as Clytie said can be "repeated".
This principle helps for me at least to complete my email processing,
because I receive too many emails per day.

Badral

Am Dienstag, den 01.07.2008, 15:02 +0200 schrieb Kai:

processing in practice. The people, who issued recently are most active

Hello Clytie,

thanks for your explation, it helps to understand. I see, that maybe
older issues are not an issue in actual builds.

But for me it seems in general (not only by unconfirmed issues) that
older problems will stay from release to release while new features
(maybe with new bugs) will be implemented. Sure, it is more fun to
implement new cool features instead of searching bugs in code many
others wrote in the past! But IMHO the trustableness for the project

now a more political thing.


interessted in getting a bug fixed quick make a new issue against the
newest build.

That's just my opinion and I am new here in QA - so don't give it to
much weight.

needs that older issues get fixed instead of new features. OK, this is To check newer issues first lets older issues stay unconfirmed and for that unsolved for a long time. I think not working the issues "first in first out" increases the occurrence of doubles, because people they are

from Clytie

Vietnamese Free Software Translation Team
http://vnoss.net/dokuwiki/doku.php?id=projects:l10n

Your opinion has weight anyway. All of us have the right to share our ideas. And newer people often have fresh ideas, and experience to share from elsewhere. :) As Badral said, this prioritization of issues is often a time- management (or general resource-management) method. It may, as you have mentioned, end up missing persistent problems, but these are likely to be reported again. I've noticed that a large proportion of older issues do get fixed in later builds. (For the Mac OSX issues, most of them.) This is encouraging, and it also helps to go through those issues and mark them Resolved. I'll be interested to hear what you find in the issue lists for other modules. if you have time, checking the status of older issues will show us if we are resolving most of them in newer builds, or not. Please report back about that. Also, the participation of the group from RedFlag should help us keep track of a lot more Calc issues. We are lucky to have so many interested new members. :)

PGP.sig
Description: This is a digitally signed message part