Launchpad itself

Ubuntu bugs marked "Fix released" before fix is generally available

Bug #827912 reported by Jonathan Lange
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

AIUI, Launchpad marks Ubuntu bugs as "Fix released" when it receives an upload claiming to fix a bug. This is good, but it would be better to mark the bug as "Fix released" only when the upload has been built & published for all architectures. Otherwise, it leads to people filing duplicate bugs, or being confused because a "fixed" bug is still not fixed.

Revision history for this message
Robert Collins (lifeless) wrote :

This is deliberate Ubuntu policy; please get techboard confirmation that this should change, until then this bug is at most incomplete, if not invalid.

Changed in launchpad:
status: New → Incomplete
Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 827912] Re: Ubuntu bugs marked "Fix released" before fix is generally available

I think there's another existing bug about 'fix released' being
unclear to users and also inconsistent across projects.

Revision history for this message
Bryce Harrington (bryce) wrote :

This issue should be included with kate's effort to re-examine the way statuses are used in Ubuntu.

Revision history for this message
Данило Шеган (danilo) wrote :

I'll change the status back and forth a bit to ensure the bug is not considered "incomplete with new responses" until we get desired behaviour from Kate and others.

Changed in launchpad:
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Launchpad itself because there has been no activity for 60 days.]

Changed in launchpad:
status: Incomplete → Expired
Jonathan Lange (jml)
Changed in launchpad:
status: Expired → Incomplete
Jonathan Lange (jml)
Changed in launchpad:
status: Incomplete → Confirmed
Revision history for this message
Jonathan Lange (jml) wrote :

I just spoke with Colin Watson while Martin Pitt & Steve Langasek were in the room. He said that closing on upload was _not_ specifically requested and that it would be better to closed after, say, the source package was published. He raised the problem of the binary not becoming available for multiple architectures at the same time, and thought that both changing status after first or last binary publish would both be options. I guess the latter would raise a question about what to do when one of the architectures fail to build.

Graham Binns (gmb)
Changed in launchpad:
status: Confirmed → Triaged
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.