Use of CLOSED in Bugzilla (was) Re: [Bug 284853] ...

[David Edmundson]

Can we continue this discussion off-bugzilla and onto our mailing
list. It's quite interesting, but not really related to that
bug-report.

CC-ing the KDE-Telepathy (where this started), and KDE-Quality mailing
list (where this discussion should be)

Backstory for those new:
 - there was a comment "is this bug closed" on a bug that was marked
as resolved. In KTp we're currently treating those two states as the
same thing.

>Well, I meant CLOSED as opposed to RESOLVED. I guess you are not using CLOSED
(yet?) either.

As I understand it in bugzilla terms, resolved is the development team
saying it's fixed. Closed is used when a QA team has accepted the
patch.

Is this correct?

Given manpower/resources, I was under the (wrong?)  impression that in
KDE we simply go to resolved and closed was in reality
unused/pointless. Certainly with my developer hat on, it seems it.

1) How _should_ we be using "closed" as opposed to "resolved" in an ideal world?
2) Which KDE teams do use it?

The only way I can see this being useful is if every time we made a
release we bulk changed anything resolved to fixed where FIXED-IN
matched the current version number. But only sysadmins/a few people
can make bulk changes like that.