Remove 'request feedback' feature for blueprints

Bug #1000642 reported by Данило Шеган
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Данило Шеган

Bug Description

The 'request feedback' feature on blueprints has never really been complete (or much used, for that matter).

For instance, emails are not sent when either the feedback is requested, nor when it is given (bug #3522).
It's also impossible to edit the feedback request, and they can only be found through the person's "requested feedback" page that nobody visits.

So, Francis has suggested getting rid of this functionality, and I jumped at the opportunity.

Fixing this bug should invalidate bug #3522, bug #3525, bug #51486, bug #125391, bug #125394, bug #125395, bug #588576 and bug #989740 (only partially).

Related branches

Changed in launchpad:
assignee: nobody → Данило Шеган (danilo)
status: New → In Progress
Revision history for this message
Curtis Hovey (sinzui) wrote :
Changed in launchpad:
importance: Undecided → High
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
Данило Шеган (danilo) wrote :

This is only the database patch that has landed. Do we need to wait for it to be rolled out before we can land the actual code changes?

Thanks for finding those other bugs as well, Curtis. #989740 is only partially fixed by this ("Registrant" link still stays there), but it'd definitely be useful to update the bug once the fix for this ultimately lands.

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

QA for this is ultimately the full test suite. No code has changed otherwise, it's just that the person merging will not insist on special handler being there for merging SpecificationFeedback rows.

tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
William Grant (wgrant) wrote :

The DB patch must indeed be deployed first; to land the code before that would prevent further code rollouts until the patch was applied.

William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-ok
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
Данило Шеган (danilo) wrote :

This looks good, I played around and couldn't break anything on qastaging.

tags: added: qa-ok
removed: qa-needstesting
description: updated
Revision history for this message
William Grant (wgrant) wrote :

The code is gone. All that remains is dropping the DB table.

Changed in launchpad:
status: Fix Committed → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-ok
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
William Grant (wgrant) wrote :

From staging:

2012-07-04 01:17:20 INFO 2209-20-1 applied just now in 0.3 seconds

tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
Revision history for this message
Данило Шеган (danilo) wrote :

William, thanks for taking care of this for me.

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

Other bug subscribers

Related blueprints

Remote bug watches

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