Confirmed users
1,351
edits
ReleaseEngineering/How To/Process release email: Difference between revisions
ReleaseEngineering/How To/Process release email (view source)
Revision as of 17:30, 10 June 2015
, 10 June 2015update with google group archives
(added detail about sns notifications) |
(update with google group archives) |
||
| Line 3: | Line 3: | ||
Note that email is not a good notification methodology, and better systems should always be preferred. However, it often is all that is available for audience which needs the notification. To minimize the pain of email notifications, follow these guidelines: | Note that email is not a good notification methodology, and better systems should always be preferred. However, it often is all that is available for audience which needs the notification. To minimize the pain of email notifications, follow these guidelines: | ||
* email should go to a unique address for the service. This can be achieved by using "plus addresses" (preferred due to positive filtering criterea). | * email should go to a unique address for the service. This can be achieved by using "plus addresses" (preferred due to positive filtering criterea). (Note: AWS SES refers to these as "labels".) | ||
** if not possible, the message MUST have a unique start to the subject field (brittle). | ** if not possible, the message MUST have a unique start to the subject field (brittle). | ||
* email should be documented on this page. | * email should be documented on this page. | ||
Some email is also routed to archives, which you may prefer to search instead of joining a list to receive emails: | |||
* [https://groups.google.com/a/mozilla.com/forum/#!forum/releng-puppet-mail releng puppet email] | |||
* [https://groups.google.com/a/mozilla.com/forum/?hl=en#!forum/release-automation-notifications release automation email] | |||
* [https://groups.google.com/a/mozilla.com/forum/?hl=en#!forum/releng-ops-trial vcs-sync email] | |||
= Index = | = Index = | ||