Merge lp:~gmb/launchpad/dont-leak-privacy-in-notifications-bug-373683 into lp:launchpad/db-devel
Status: | Merged |
---|---|
Merged at revision: | 9442 |
Proposed branch: | lp:~gmb/launchpad/dont-leak-privacy-in-notifications-bug-373683 |
Merge into: | lp:launchpad/db-devel |
Diff against target: |
188 lines (+148/-7) 2 files modified
lib/lp/bugs/adapters/bugchange.py (+34/-6) lib/lp/bugs/tests/test_bugchanges.py (+114/-1) |
To merge this branch: | bzr merge lp:~gmb/launchpad/dont-leak-privacy-in-notifications-bug-373683 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Leonard Richardson (community) | code | Approve | |
Review via email: mp+27051@code.launchpad.net |
Commit message
Private bug summaries will no longer be included in bug duplication notifications.
Description of the change
This branch fixes bug 373683 by preventing bug notifications generated when a bug is marked a duplicate of a private bug from including the private bug's summary.
I've made the following changes:
* lib/lp/
* I've updated BugDuplicateChange to make it not include private bug summaries.
* lib/lp/
* I've updated the tests to test the above change.
I did consider refactoring BugDuplicateCha
r=me with some minor changes.
Did you mean to merge this with devel rather than db-devel? I make that mistake all the time.
Rather than bikeshedding the logic of the message generator, I suggest you just define four constants so you don't write the same string multiple times.
75 # extra notificationse by mistake.
118 # extra notificationse by mistake.
(Should be 'notifications')