revision emails should omit irrelevant merge proposals
Bug #504356 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Tim Penhey | ||
Bug Description
Revision emails mention old merge proposals that are no longer relevant, and this can be distracting.
On the other hand, it's hard to determine what "relevant" means. It has been proposed that only the most recent merge proposal is relevant, but older proposals could be relevant if they indicate problems with the latest merge proposal or the code review process. For example, if a branch had been rejected as a bad idea, and then later merged.
Perhaps we should simply hide superseded proposals?
Related branches
lp:~thumper/launchpad/only-show-latest-bmp-in-revision-mail
- Michael Hudson-Doyle: Approve
-
Diff: 126 lines (+48/-16)2 files modifiedlib/lp/code/model/branchjob.py (+24/-12)
lib/lp/code/model/tests/test_branchjob.py (+24/-4)
| tags: | added: email |
| Changed in launchpad-code: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: trivial |
| Changed in launchpad-code: | |
| status: | Triaged → Fix Committed |
| Changed in launchpad-code: | |
| milestone: | none → 10.02 |
| Changed in launchpad-code: | |
| assignee: | nobody → Tim Penhey (thumper) |
| Changed in launchpad-code: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
