FixReleased should be locked against reopening

Bug #664096 reported by Deryck Hodge
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Deryck Hodge

Bug Description

The bug task status FixReleased should be locked so that only bug supervisor or the original reporter can transition a bug away from FixReleased.

Tags: lp-bugs qa-ok

Related branches

Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
Changed in malone:
milestone: none → 10.11
tags: added: qa-needstesting
Changed in malone:
status: In Progress → Fix Committed
status: Fix Committed → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Incremental fix
Deryck Hodge (deryck)
tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
Robert Collins (lifeless) wrote :

Garh incremental branches.

Changed in malone:
status: In Progress → Fix Released
status: Fix Released → In Progress
tags: removed: qa-ok
tags: added: qa-needstesting
tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
tags: added: qa-needstesting
removed: qa-ok
Changed in malone:
status: In Progress → Fix Committed
Deryck Hodge (deryck)
tags: added: qa-ok
removed: qa-needstesting
Changed in malone:
status: Fix Committed → Fix Released
Revision history for this message
Oliver Grawert (ogra) wrote :

what is the justification for that change ? it would be really nice to put the reason that caused such a decision into the bug description, note that there are teams with only one supervisor (but a bunch of developers that work on bugs without being supervisors) with that change you add an artificial bottleneck to such teams (and put extra paperwork onto the bug supervisor).

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 664096] Re: FixReleased should be locked against reopening

@Oliver contentious bugs in high volume projects/packages suffer when
a bug looks superficially like a users symptoms and they say 'hey,
this has regressed' - e.g., 'black screen on boot' : yet there can be
hundreds of discrete causes causing that symptom.

Is it unreasonable to have a team as bug supervisor if you want to
allow a wide spread of developers to do anything with bugs. Note too
that the original bug *filer* will be able to un-release a bug : after
all they are the person with the original symptoms.

Revision history for this message
Martin Pool (mbp) wrote :

@ogra https://bugs.launchpad.net/launchpad/+bug/887875 for problems caused by this approach.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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