"Fix committed" bugs are treated as "resolved" bugs
Bug #28698 reported by
Lucas Nussbaum
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Brad Bollenbach |
Bug Description
"Fix committed" bugs are treated as "resolved" in some places (for example: the default bug listing). This is wrong, since those bugs still require human interaction (an upload) before one can really forget about them.
Changed in malone: | |
assignee: | nobody → bradb |
Changed in malone: | |
status: | Confirmed → In Progress |
Changed in malone: | |
status: | In Progress → Fix Committed |
Changed in malone: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Same problem with "Fix released" when the package comes from a Debian package. For example, this bug: /launchpad. net/distros/ ubuntu/ +source/ qt4-x11/ +bug/6525
https:/
It is treated as resolved because its status is "Fix released". Indeed this package is released in Debian, but it is not yet uploaded in Ubuntu (pending).
Do we need another status "Uploaded"?
The meaning of the field status is not correctly explained, see /launchpad. net/products/ soyuz/+ bug/29596
https:/