RESOLVED vs CLOSED

Raphael Kubo da Costa kubito at gmail.com
Sat Jan 15 19:30:15 GMT 2011


On Sat, Jan 15, 2011 at 3:15 PM, Hugo Pereira Da Costa
<hugo at oxygen-icons.org> wrote:
> Hello all,
> sorry for this newbye question.
> I was pointed out that RESOLVED bugs on bugs.kde.org can be further tagged as
> CLOSED. ... which I did not know.
>
> Right now, there are 432 bug reports related to oxygen which are RESOLVED, but
> not CLOSED.
>
> What exactly is the policy on tagging them as CLOSED, with respect to RESOLVED
> ? (so far I've been using the second pretty much in place of the first)
>
> Should I go through all of them and CLOSE them ? Or just the ones that are
> only FIXED, or INVALID, or UPSTREAM ?

According to https://bugs.kde.org/page.cgi?id=fields.html it's mostly
QA-related. As we don't have a policy for this, RESOLVED is usually
just fine.




More information about the kde-core-devel mailing list