[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Final bugzilla status
|
Hi,
So it looks that the correct way of working is:
Resolved -> checked in
Verified -> it works
Closed -> no action in code, the issue has gone or not gone but we stop working on it.
I filed a bug first against cross project with the final aim to move it over to webmaster to have the help text updated [1].
Thanks,
Wim
On Mon, May 28, 2012 at 8:29 PM, Eric Moffatt
<emoffatt@xxxxxxxxxx> wrote:
Different projects may have different
conventions but for the Platform UI group is works this way:
Resolved -> Fixed Means that
the code to fix the defect has been committed
Then we wait for that code to come out
in some later build and test the fix to make sure that it's actually in
the built version and change the status to
Verified -> Fixed Meaning that
we've ensured that the fix works. This prevents us from situations where
the code may work on someone's machine due to changes in the code in their
workspace (which may not have been committed)...
The various 'Closed' states indicate
that we are no longer working on the defect for one reason or another but
there are no code changes involved...
Onwards,
Eric
Hi,
I have a question about the final bugzilla status for
resolved bugs. I was under the impression that it was CLOSED+FIXED. However,
since there are two other statuses in bugzilla RESOLVED+FIXED
and VERIFIED+FIXED I decided to check the helptext [1] to see what they
mean. There it says that VERIFIED+FIXED is the last status.
So what does CLOSED mean? Is it higher in the cycle than
VERIFIED or does it mean something else?
Thanks,
Wim Jongman
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
