3.15 Release: Product release tasks

[christinaforney]

• [x] Release blog post
• [x] Release email
• [x] Release tweet

At the start of the month (2020-04-01)

• [x] Create draft blog post Google doc in Sourcegraph shared
  • [x] View each team's release deliverables to generate the outline of the blog post
  • [x] Share link to blog post doc in #progress Slack channel, asking Team leads to review
• [x] Create draft tweet
• [x] Create draft email
• [x] Link to the blog post, email and tweet

Create calendar events

Add events to the shared Release Schedule calendar in Google and invite team@sourcegraph.com:

• [x] Blog post draft ready for review (5 days before release)
• [x] Final blog post changes/suggestions must be submitted (3 days before the release)
• [x] Blog post / tweets go live (the specific date we plan to do this, often not the 20th when it is a Friday).

In the first week

• [x] Fill out each section based on the deliverables to first draft quality
• [x] Think about what media (e.g. screenshot, screencast) will accompany the section content

In the second week

• [x] Remove motd previous release promotion from Sourcegraph.com global settings
• [x] Confirm with each team that the planned deliverables are still on track to be announced in the blog post.

10 working days before release

• [ ] Post the blog post draft to #dev-announce: The blog post draft for 3.15 is ready, please review your parts are accurate and provide feedback by <DATE>: <link>
• [x] Tweet written
• [x] Email written
• [x] Write a warning at the top of the Google doc: The blog post has been finalized and moved to Markdown, further changes here will not be reflected. Contact @ryan-blunden for suggestions.
• [x] Export blog post from Google docs to Markdown and create a new branch and draft pull request in sourcegraph/about, using the release blog post template
• [ ] Send blog post, and email to copy editor

5 working days before release

• [x] Start producing screenshots, diagrams, and screencasts for each blog post section

3 working days before release

• [x] Check for any last minute release changes that affect the blog post, e.g. last minute feature removal
• [x] Finalize screenshots, diagrams, and screencasts
• [x] Blog post approved
• [ ] Email approved
• [ ] Tweet approved

Day of release

• [x] Publish blog post once the final release is cut, and docs version change is deployed
• [x] Publish tweet:
  • [x] Pin new release tweet
  • [ ] Confirm with Marketing if tweet will be promoted
• [x] Send email in HubSpot
• [x] Create new notice in Sourcegraph.com global settings

  "notices": [
   {
     "message": "Sourcegraph 3.15 is now available! Check out the [3.15 release blog post](https://about.sourcegraph.com/blog/sourcegraph-3.15) for more details.",
     "location": "top",
     "dismissible": true
   }
  ]

• [x] Use tweet or email content for post on the LinkedIn Sourcegraph company page
• [x] Put notification in #dev-rel Slack channel with links to blog post and tweet

[uwedeportivo]

Dear all,

This is your release captain speaking. 🚂🚂🚂

Branch cut for the 3.15 release is scheduled for tomorrow.

Is this issue / PR going to make it in time? Please change the milestone accordingly. When in doubt, reach out!

Thank you