Comment 3 for bug 971
Revision history for this message
| Matt Zimmerman (mdz) wrote Re: [mpt@canonical.com: [Bug 971] Rename New/Accepted statuses as Unconfirmed/Confirmed, and other tweaks] | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
On Thu, Dec 01, 2005 at 08:59:45PM -0200, Christian Robottom Reis wrote:
> UI and functionality change. I'd like to get sign-off from you on this
> proposal.
> [...]
> To resolve this confusion and encourage better Malone workflow, bradb, mpt, and kiko have concluded that Malone should have these states:
> "Unconfirmed" (renamed from "New")
> "Needs Info" (renamed from "NeedInfo")
> "Rejected" (no change)
> "Confirmed" (renamed from "Accepted")
> "In Progress" (new state)
These seem reasonable.
> "Fixed" (renamed from "PendingUpload")
> "Released" (renamed from "Fixed").
It is very confusing for users to see a bug marked "Fixed" but to be unable
to get the fix anywhere. I recommend that the final state continue to be
called "Fixed" or "Closed", as these are widely used terms in bug trackers
with a well-understood meaning.
I would support renaming PendingUpload to something more meaningful, which
indicates more clearly "someone has implemented a fix, but it's not
available in the usual place yet".
The states we currently have in Bugzilla are:
NEW "Unconfirmed"
ASSIGNED "Confirmed
NEEDINFO "Needs Info"
UPSTREAM This is handled by other means in Malone(?)
PENDINGUPLOAD Could be named better
RESOLVED/FIXED "Fixed"
RESOLVED/... Rejected
--
- mdz