Merge requests can spam teams
Bug #261494 reported by
Matt Zimmerman
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Tim Penhey | ||
Bug Description
Examples:
https:/
https:/
Both of these were sent to all Ubuntu Core Developers (ubuntu-core-dev).
It was suggested that perhaps these requests should not be allowed to be sent to teams, or to solve this issue more generally for mail sent to teams.
Revision history for this message
| Jonathan Lange (jml) wrote | #1 |
| Changed in launchpad-bazaar: | |
| importance: | Undecided → High |
| status: | New → Incomplete |
| Changed in launchpad-bazaar: | |
| assignee: | nobody → thumper |
| status: | Incomplete → In Progress |
Revision history for this message
| Paul Hummer (rockstar) wrote | #2 |
| Changed in launchpad-bazaar: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad-bazaar: | |
| status: | Fix Committed → Fix Released |
| milestone: | none → 2.1.11 |
To post a comment you must log in.
For many upstream projects, it makes a lot of sense for the entire team that owns the branch to be notified—it should be equivalent to patches being sent to a project mailing list. I'm not sure what to do for your case.
Matt, if branch ownership were separated from ability to write to a branch, would that change this bug? Would apport trunk be owned instead by a smaller team?