I assume the text quoted below is from
EMFT’s build process.
This doesn’t seem to match how
Bugzilla recommends using status codes.
For example, Bugzilla defines ASSIGNED as:
This bug is not yet
resolved, but is assigned to the proper person. From here bugs can be given to
another person and become NEW, or
resolved and become RESOLVED.
The Resolved status is one of the
following: FIXED, INVALID, WONTFIX, DUPLICATE, WORKSFORME, MOVED.
So, based upon Bugzilla’s status
code definitions (https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#status),
I would assume the normal flow for an issue to be:
NEW è ASSIGNED è FIXED è VERIFIED è CLOSED
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On
Behalf Of Marcin Okraszewski
Sent: Tuesday, October 03, 2006
11:35 AM
To: Corona development
Subject: [corona-dev] The
"assigned" status.
Here is the citation from
email "CVS Commit Comments" which says we should set
"Assigned" status after commiting a fix into CVS. At least I
undestand it in this way.
- Browse to the bug's webpage, and assign
it the status Assigned. This tells the release notes generator that this is a bug which
should be included in the release notes this week. Your bugzilla comment
could be something like:
Committed to CVS
Marcin
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
