Merge lp:~gary/launchpad/bug164196-1 into lp:launchpad/db-devel
Status: | Merged |
---|---|
Approved by: | Gary Poster |
Approved revision: | no longer in the source branch. |
Merged at revision: | 10215 |
Proposed branch: | lp:~gary/launchpad/bug164196-1 |
Merge into: | lp:launchpad/db-devel |
Diff against target: |
293 lines (+50/-52) 11 files modified
database/schema/comments.sql (+1/-0) database/schema/patch-2208-46-0.sql (+8/-0) lib/lp/bugs/configure.zcml (+0/-6) lib/lp/bugs/doc/bugnotifications.txt (+16/-0) lib/lp/bugs/interfaces/bug.py (+5/-2) lib/lp/bugs/interfaces/bugnotification.py (+6/-1) lib/lp/bugs/model/bug.py (+6/-4) lib/lp/bugs/model/bugnotification.py (+4/-2) lib/lp/bugs/subscribers/bug.py (+0/-10) lib/lp/bugs/subscribers/bugactivity.py (+2/-26) lib/lp/bugs/tests/test_bugnotification.py (+2/-1) |
To merge this branch: | bzr merge lp:~gary/launchpad/bug164196-1 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robert Collins (community) | Approve | ||
Stuart Bishop (community) | db | Approve | |
Данило Шеган (community) | code | Approve | |
Review via email: mp+49973@code.launchpad.net |
Commit message
add a link from bug notifications (which are about sending emails) to bug activities (which are about keeping an activity log for each bug, and are more normalized in their description of what happened) as part of work towards bug 164196.
Description of the change
This is the first of three branches that address bug 164196, and one of two that have a database patch. The other two are lp:~gary/launchpad/bug164196-2 and lp:~gary/launchpad/bug164196-3. My pre-implementation call for these changes was with Graham Binns.
The primary job of this branch is to add a link from bug notifications (which are about sending emails) to bug activities (which are about keeping an activity log for each bug, and are more normalized in their description of what happened). This allows me in branch 2 to use the bug activity records to determine what was done and undone.
To do this, I added an activity column in the database, and made the code that generates bug notifications and bug activities synchronize the two. The first of those is straightforward, but the second has some wrinkles.
I'll highlight what I did for the second part of the task in bullet form.
* In the set of bug notifications, I added an activity object to the signature of addNotification.
* Bug target's addCommentNotif
* I combined lp.bugs.
In the course of doing this, I discovered that lp.bugs.
Thank you
<danilos> gary_poster, re -1, in lib/lp/ bugs/model/ bug.py you modify addCommentNotif ication to add activity parameter, but you don't modify addChange which I believe does a similar thing for non-comment changes — is that intentional or not?
<gary_poster> danilos, intentional. addChange uses change objects, which handle activities themselves