For Developers‎ > ‎

Status Update Email Best Practices

General suggestions

  • Send to list with +status, e.g.
  • Minimize boilerplate subject line.
  • Summarize highlights in subject, or as the first line of the email.
  • Main content follows as a bullet list of key status updates.
  • Every 2 weeks works well for many projects. Adjust as appropriate given the news of an update.
  • For feature status updates, link the feature on
  • Optimize for skimmability.



Subject: Bluetooth Status - Experiment targeting M51, Opera demoed at MWC.

Web Bluetooth provides Bluetooth GATT Access to web apps.