This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: your RESOLVED->CLOSED changes


Giovanni Bajo wrote:
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> wrote:


As a side-note: I moved several PRs of mine to RESOLVED, incorrectly
assuming this would "close" them.

Clearly, this was operator error on my side, but it's a data point that
we might consider removing the distinction between RESOLVED and CLOSED.


I don't think it's your "fault", because this is exactly what Bugzilla lets
you do right now. I'm doing the same as well right now.  It's not such a big
issue because we have so many bugs in RESOLVED status, so a batch change is
needed anyway, somewhere in the future.

Right now, in order to change to CLOSED, you need to edit the bug two times,
and this is suboptimal. If we agree for removing the distinction, we'll
surely ask Danny to update the system accordingly (the best way is to modify
the commit actions so that they immediatly switch to the CLOSED status
instead of switching to the RESOLVED status).

If we keep 'verified' (as I suggested), I would still approve of this. The commit actions would have "Close, setting resolution to X" and "Verify fixed (but not in a release), setting resolution to X".


The "resolved" state is not useful in the long run to a project with no separate QA team.

Giovanni Bajo


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]