Merge lp:~sinzui/launchpad/contact-new-maintainer into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Curtis Hovey on 2012-10-05 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 16104 |
| Proposed branch: | lp:~sinzui/launchpad/contact-new-maintainer |
| Merge into: | lp:launchpad |
| Diff against target: |
274 lines (+54/-28) 2 files modified
lib/lp/registry/subscribers.py (+10/-9) lib/lp/registry/tests/test_subscribers.py (+44/-19) |
| To merge this branch: | bzr merge lp:~sinzui/launchpad/contact-new-maintainer |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Abel Deuring (community) | code | 2012-10-05 | Approve on 2012-10-05 |
|
Review via email:
|
|||
Commit Message
Send licensing email to new project maintainer.
Description of the Change
Lp is sending licensing emails to the project registrant, but the
registrant may have made someone else the maintainer. The licensing
jobs already use the maintainer, so there is a chance of confusion
when the registrant is not a member of the maintainer team.
-------
RULES
Pre-
* Use the project maintainer, not the registrant when sending
the initial email about licensing issues.
* The emails already use neutral language to deal with user and teams.
QA
* Clear the staging inbox so that you can find the email.
* Visit https:/
* Register a project with a proprietary license and set a team as the
maintainer.
* Check the staging inbox and verify there is a message addressed
to the team admins.
LINT
lib/
lib/
TEST
./bin/test -vvc lp.registry.
IMPLEMENTATION
I first updated LicenseNotification to ignore the user and instead use
the product.owner. I then removed the user argument since it was unused.
Since the code does not adapt the event.user, tests do not need to be
logged in.
lib/
lib/
