{% if not feature.owner %}None{% endif %}{% for owner in feature.owner %}{% if forloop.last %}{{owner}}{% else %}{{owner}},{% endif %}{% endfor %}
{% if feature.spec_link %}{{feature.spec_link}}{% else %}None{% endif %}
{{feature.summary}}
Fill me in.
Firefox: {{feature.ff_views.text}}
Internet Explorer: {{feature.ie_views.text}}
Safari: {{feature.safari_views.text}}
Web developers: {{feature.web_dev_views.text}}
If you don't have a launch tracking bug or row in the feature dashboard, include in this email links to relevant specs, standards discussions, or documentation about support for the feature in other browsers.Do you anticipate adding any ongoing technical constraints to the codebase while implementing this feature? We prefer to avoid features which require or assume a specific architecture. For most features, the answer here is "None."If no, explain why certain platforms will not be included in your implementation.
{% if feature.bug_url %}{{feature.bug_url}}{% else %}None{% endif %}
{{edit_url}}"No" - you will be implementing your feature behind a runtime flag and sending an Intent to Ship email when you're ready to enable by default.
"Yes" - your change is small and you'd like to ship enabled-by-default immediately. Per the launch process for new features, you'll need LGTMs from 3 API OWNERS before shipping. If "yes," please change the title of the email to "Intent to Implement and Ship: ...".