Mattermost Handbook
Need help?How to spend company moneyHow to update the HandbookRelease overview
0.2.1
0.2.1
  • Mattermost Handbook
  • Company
    • About Mattermost
      • List of terms
      • Business model
      • Mindsets
    • "How to" guides for staff
      • How to set up a 1-1 channel
      • How to update the handbook
      • How to manage Handbook notifications
      • How to change mobile device
        • How to handle a lost mobile device
      • How to do a mini-retrospective
      • How to autolink keywords in Mattermost
  • Operations
    • Company operations
      • Areas of Responsibility
      • Mattermost Leadership Team (MLT)
        • MLT cadence
      • Company measures
        • Metrics definitions
        • FY23 goals board
        • MLT metrics
      • Company cadence
      • Company policies
        • Community response policy
        • Security policy
      • Company processes
        • Issue/solution process
        • Company agreements
        • Publishing
          • Public web properties
          • Publishing guidelines
            • Brand and visual design guidelines
            • Voice, tone, and writing style guidelines
              • Contribute to documentation
            • Confidentiality guidelines
          • Post-publication quality control process
      • Handbook processes and policies
        • Handbook onboarding
      • Fiscal year planning
    • Research and Development
      • Organization
        • Tech Writing
        • Data engineering
        • Delivery
        • Cloud Platform
        • Site Reliability Engineering
        • GRC
        • Product Security
        • Security Operations
      • Processes
        • Feature Labels
      • Product
        • Product planning
          • Product philosophy and principles
          • Prioritization process
          • Release planning process
          • Roadmap views
          • Release plan
          • Launch plan
          • Feature requests
        • Development process
          • Mobile feature guidelines
          • Deprecation policy
          • Mattermost software requirements process
          • Jira ticket lifecycle
          • Creating new Jira bug tickets
            • Priority levels for tickets
            • Jira fix versions
        • Release process
          • Release overview
          • Feature release process
          • Dot release process
          • Security release process
          • Mobile app release process
          • Desktop app release process
          • Release tips
          • Release scorecard definitions
        • How-to guides for Product
          • How to use productboard
          • How to record a roadmap video
          • How to update integrations directory
          • How to write a feature release announcement
        • Product Management team handbook
          • Product Management Areas of Ownership
          • Product Manager onboarding
          • Product Manager levels
          • Professional development
        • Product Design team handbook
          • Product Design levels
        • Technical Writing team handbook
          • Work with us
          • User interface text guidelines
          • Documentation style guide
          • Our terminology
          • Guidelines for PMs and developers
          • Guidelines for community contributions
          • Technical Writer levels
          • Docathon 2021
            • Getting started with contributing
        • Growth
          • A/B testing methodology
          • PQL definition
        • Analytics
          • Product Analyst Engineer levels
          • Looker
            • Dashboards
            • Explores
          • Telemetry
        • Developer relations
        • Product team hangouts
      • Engineering
        • Infrastructure engineering
          • Cloud infrastructure cost KPIs
          • Cloud data export process
          • Cloud churn process
          • Reliability Manifesto
          • Production Readiness Review
          • Infrastructure Library
        • Integrations team processes
        • Plugin release process
        • Data Engineering
        • Sustained Engineering
          • On call
        • How to go to a conference
        • Public speaking
        • Core contributor expanded access policy
      • Quality Assurance
        • QA workflow
        • QA testing tips and tools
        • Rainforest process
    • Messaging and Math
      • How-to guides for M&M
        • How to create release announcements
        • How to create screenshots and GIFs
        • How to write Mattermost case studies
        • How to write guest blog posts for Mattermost apps and services
        • How to write Mattermost recipes
        • How to compose tweets
        • How to create a split test for web page
        • How to run meetups
        • How to run executive dinners
      • Checklists for M&M
        • Blog post checklist
        • Bio checklist
      • Mattermost websites
      • Demand generation reporting
      • M&M Asana guidelines
      • Content marketing
        • How to use the editorial calendar
        • Content development and distribution
        • Video content guidelines
        • How to contribute content
    • Sales
      • Deal Desk
      • Partner programs
      • Lead management
    • Deployment Engineering
      • Overview
      • Workflows
      • Frequently Asked Questions
      • Playbook for MME Sev 1 Outages
      • Status Update Template
    • Program Management
    • Customer Success
      • Customer Support
    • Legal
      • Contracts
      • Ironclad Basics
        • Company-Wide Workflows
        • Sales Contracts and Workflows
        • Signing a Contract and Contract Repository
    • Finance
      • Budget
      • How to use Airbase
        • Access Airbase
        • Navigate Airbase
        • How to submit a purchase request
        • How to submit a reimbursement request
        • How to review a reimbursement request
        • Vendor portal guide
        • Frequently asked questions
      • Onboarding
        • Vendor onboarding
        • ROW staff onboarding
      • Staff member expenses
        • How to spend company money
        • How to spend company money: Internships
        • Corporate credit card policy
        • How to access Airbase
        • Gifting policy
        • How to book airfare and travel
        • How to reimburse the company
        • How to convert currencies
        • How to get paid
      • Arrange a Bounty Program
      • Naming files and agreements
      • Risk management
        • Mattermost U.S. consulting agreements
      • Operations playbook
    • Security
      • Policies
      • Privacy
        • Data deletion requests
        • Data subject access requests
      • Product Security
        • Product Vulnerability Process
        • Working on security-sensitive pull requests
        • Secure Software Development guide
      • Security Operations
        • User guides
    • Workplace
      • PeopleOps
        • HR cadences
        • HR systems
        • HR Processes
        • Working at Mattermost
          • Onboarding
            • Things everyone must know
            • Staff onboarding
            • Engineer onboarding timeline and expectations
            • Manager onboarding
            • Frequently asked questions
          • Learning and development
          • Mattermost communication best practices
          • Paid time off
            • Out of office email example
          • Travel
            • Business travel insurance
          • Leaves of absence
            • Pregnancy leave
            • Baby bonding parental leave
            • Jury duty
          • Workplace program
          • Relocation
          • Total rewards
        • Performance reviews
          • Formal review process
          • New staff performance review
          • Informal review process
        • Transfers and promotions
        • Offboarding instructions for managers
        • People compliance
      • People policies
      • Groups
        • Staff Resource Groups
      • Approvals and iteration
      • IT
        • IT helpdesk
        • Hardware and software purchases
        • Hardware buy back policy
        • Software systems
  • Contributors
    • Contributors
      • Equity, diversity, and inclusion
      • How to contribute to Mattermost
        • Community Content program
        • Documentation contributions
        • Help Wanted tickets
        • Localization
        • Contribution events
      • Mattermost community
      • Contributor kindness
      • Community systems
      • Guidelines and playbooks
        • Social engagement guidelines
        • Contribution guidelines and code of conduct
        • Mattermost Community playbook
        • How to run a Hackathon
        • Hacktoberfest event organizer guide for Mattermost
    • MatterCon
      • Staff information privacy management
      • Mattermost events code of conduct
      • MatterCon2021
    • Join us
      • Ice-breakers
      • Help Wanted tickets
      • Localization
      • Mattermost GitHub sponsorship
      • Things candidates should know
      • Staff recruiting
      • Recruiting cadences
        • Product Manager hiring process
      • Exec recruiting
        • EA logistics
  • Help and support
    • Contact us
Powered by GitBook
On this page
  • Overview
  • Timeline
  • Feature Headline
  • Feature Benefit
  • Feature Details
  • Feature Image
  • Feature Resources
  • How to Write a Release Tweet

Was this helpful?

Edit on Git
Export as PDF
  1. Operations
  2. Research and Development
  3. Product
  4. How-to guides for Product

How to write a feature release announcement

PreviousHow to update integrations directoryNextProduct Management team handbook

Last updated 3 years ago

Was this helpful?

This document outlines how to write a release announcement and release tweets for a feature. These are used at the release day in our release newsletter and Twitter.

Each Product Manager is responsible for writing a release announcement for every feature, integration, or announcement they want included in the release newsletter.

.

Overview

It's important to think of the release announcement as a press release. We're communicating changes to our current and prospective customers so we want it to be exciting as well as informative. The release announcement is a coordinated document, with each Product Manager contributing their own features as sub-headings. The headline and first paragraph will be written by PM leads and the CPO after all other features have been provided.

Note: Consider using this information in productboard for your features to validate the messaging and to keep consistency across channels.

Timeline

A release announcement for each feature should be started early in the product planning process. Each Product Manager is directly responsible for writing the announcement for each of their features. For large product features or new products, a PRFAQ should be completed. For smaller features, a “mini-PRFAQ” should be completed in the form of a blog post. Below are the expected deadlines ("T-X" dates don't include holidays/weekends):

A. (T-minus 14 working days) Outline

  • Release Manager provides an outline of the release announcement and deadlines for Product Managers, along with a heads-up for Director of Product Marketing that the blog post is coming. Release Manager also adds deadlines to the PM Weekly Sync Agenda.

B. (T-minus 9 working days) First draft

  • A draft of the release announcement and tweets are completed by Product Managers. Product Managers prepare the release announcement from their 2-pager documents. Product Managers are reminded of the deadline in the weekly Monday PM Sync meeting. The T-9 deadline should be the 1st Monday of the month for our Roadmap call (this will either be T-9 or the first Monday of the month, whichever comes earlier).

C. (T-minus 8 working days) Lead Product Managers' Review

  • Product Management leads do a final review on the release announcement and prepare the headline and byline content.

D. (T-minus 7 working days) Product Marketing Director and Communications Director Reviews

  • The PM-approved draft will be provided for review to the Director of Product Marketing and to the Director of Communications. Katie Wiersgalla (@wiersgallak) provides the release announcement copy for review and relays edits back to the Product Management team via the Product Manager's internal channel.

E. (T-minus 2 working days) Marketing Preparation

  • Katie provides the final and approved release announcement copy for Amy Blais (@amy.blais) to give to the marketing team.

F. (T-minus 0 working days) Release

  • The release announcement is published. T-0 is based on the Release Day in the Mattermost Release Dates calendar.

Feature Headline

The headline for your feature should start with a verb and describe what the feature allows customer to do and the edition it's provided in.

Example: Sync Office 365 Calendar status with Mattermost (E20 edition)

Feature Benefit

A quick summary sentence should follow with the benefit the feature provides.

Example: Enable your users to get more control over their schedule without leaving Mattermost.

Feature Details

Next, describe in more detail how the feature works and what functionality is included. This could take the form of a bulleted list or a few more sentences.

Example:

With the new two-way Microsoft Office 365 Calendar integration feature, your users can now:
 - See a daily summary of their calendar events
 - Sync their Office 365 Calendar status automatically into Mattermost (e.g., “Away” if you have a meeting on your calendar)
 - Accept or decline calendar event invites from within Mattermost

Feature Image

Feature Resources

Finally, add a link to the documentation, forum post, or repository as appropriate for the user to get more information on the feature. Also, be sure to provide a line to thank the contributors who helped provide the feature.

How to Write a Release Tweet

Product Managers are also responsible for drafting the tweets that correspond to your features.

Each tweet should start with Mattermost Release vx.xx now… or Mattermost mobile app release vx.xx now… and should describe the action the new feature allows them to do. This should be very similar to the headline written in the release announcement. Tweets should include the relevant hashtags: #mm524m, #opensource, #sre, #devops, #mattermost (where #mm524 is the release number).

Example Tweet: Mattermost Release v5.24 now lets you view and manage your team or channel members from the System Console. #mm524 #opensource #sre #devops #mattermost

Then, add actual screenshots or GIFs of the feature. Abide by our guidelines for screenshots provided .

Here is an example of a previously completed release announcement
here