Mail notifications for administrative actions
Bug #42831 reported by
Matt Zimmerman
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
I would like for a contact (such as a dapper-
- Override changes (e.g., packages moving between main and universe)
- Package removals
- New package acceptance
- Buildd admin actions (retries, dep waits, etc.)
This would help both with transparency and auditing of these actions.
Changed in soyuz: | |
assignee: | Celso Providelo (cprov) → nobody |
tags: | added: feature |
Changed in launchpad: | |
assignee: | nobody → 杨敏 (mandy9337) |
status: | Triaged → Invalid |
security vulnerability: | no → yes |
visibility: | public → private |
Changed in launchpad: | |
status: | Invalid → Confirmed |
security vulnerability: | yes → no |
visibility: | private → public |
Changed in launchpad: | |
assignee: | 杨敏 (mandy9337) → nobody |
status: | Confirmed → Triaged |
Changed in launchpad: | |
importance: | High → Low |
tags: | added: email |
To post a comment you must log in.
Right, let's specify what will be required:
* An administrative mailing list for distribution, let's say "<distro> -changes- admin"
* Overrides changes: We will have a ISSPPH/ ISBPPH. reason field and change-override tool will send an email to the admin ML containing a report of the executed action.
* Package Removal: The same ISSPPH/ ISBPPH. reason field will be used, remove-package tool will send email as change-override.
* New Package acceptance: queue tool already send email to the <distro>-changes maillisting, should we Bcc the admin ML as well ?
* Build admin actions: it will be part of the build-failure- notification spec, but I'm not sure we should collapse the messages in the admin ML, buildd-failures are supposed to have their own ML.
Apart of small details, we can do this quickly before edgy release, Maybe we should right a small/straightf orward specification for this.