BUG INFORMATION
Some time we are searching for the bug but we are not consider the Status
Part for that Bug, it says the status for bug is valid or not.
OPEN basically means "Development is still working on
it."
·
NEW means freshly
reported
·
ASSIGNED means a developer is
named and "on the hook" to make a fix
·
OPEN
means
that there is a branch checked out and work is being actively done on the bug
·
INFORMATION
REQUIRED means that development is stalled until information can be collected
from the bug reporter.
·
MORE
means
that some branches are fixed, but others are not yet fixed. The fix is
basically done, but being ported to other releases.
·
DUPLICATE means that this bug
is reporting a behavior already described by an open bug (bugs in that state
point to the "root" bug).
Rarer states
·
FORWARDED means it is in the
process of being transferred to another project.
·
POSTPONED means that action is
deferred until a future date (like a later release)
·
WAITING (I have never seen
this state used)
·
SUBMITTED (I have never seen
this state used)
·
HELD means that there is
something blocking any further action from being taken. Rarely used.
FIXED means development is done working on
it.
·
RESOLVED means the bug is
written and committed.
·
VERIFIED means that it has
cleared testing. Not all test groups use the bug database, so some bugs
stop at RESOLVED. That doesn't mean they aren't tested, only that the
test group for that project does not updated the bug database.
TERMINATED means development will not work in it and no further
action will be taken.
·
CLOSED means that Cisco
acknowledges the observed behavior, but refuses to fix it. This is
usually the case for older software which is no longer maintained or very minor
fixes that could cause more thouble than good.
·
JUNKED means that the
behavior reported is the result of a misconfiguration or misunderstanding of
the behavior in question, or else the bug is reporting an intentional design
choice.
·
UNREPRODUCIBLE means that the bug,
as reported, cannot be replicated and therefore cannot be fixed. This may
be a problem that arose from a hardware issue or a one-shot rare event that
never happens again.
A typical bug flow looks like this:
No comments:
Post a Comment