Confirmed users
1,364
edits
ReleaseEngineering/How To/Process release email: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Process release email (view source)
Revision as of 17:27, 17 April 2015
, 17 April 2015added lore and common practice
m (add chromecast fragment) |
(added lore and common practice) |
||
| Line 1: | Line 1: | ||
{{Release Engineering How To|Process email to release@}} | {{Release Engineering How To|Process email to release@}} | ||
This is a list of automatically generated emails you should expect to receive as a release engineer at mozilla. It is not complete | This is a list of automatically generated emails you should expect to receive as a release engineer at mozilla. It is not complete. | ||
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). | |||
** if not possible, the message MUST have a unique start to the subject field (brittle). | |||
* email should be documented on this page. | |||
= Index = | = Index = | ||