Skip to content

3.10 Release blog post tasks

Created by: christinaforney

3.10 Release: DevRel tasks

At the start of the month (2019-11-01)

  • Create draft blog post Google doc in Sourcegraph shared

    • View each team's release deliverables to generate the outline of the blog post
    • Share link to blog post doc in #progress Slack channel, asking Team leads to review

  • Create draft tweet

  • Create draft email

  • Link to the blog post, email and tweet

Create calendar events

Add events to the shared Release Schedule calendar in Google and invite [email protected]:

  • Blog post draft ready for review (5 days before release)
  • Final blog post changes/suggestions must be submitted (3 days before the release)
  • 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

  • Confirm with each team that the planned deliverables are still on track to be announced in the blog post.
  • Fill out each section based on the deliverables to first draft quality
  • Think about what media (e.g. screenshot, screencast) will accompany the section content

In the second week

  • Remove motd previous release promotion from Sourcegraph.com global settings
  • Post the blog post draft to #dev-announce: `The blog post draft for is ready, please review your parts are accurate and provide feedback by :
  • Tweet written
  • Email written
  • 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.
  • 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

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

3 working days before release

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

Day of release

  • Publish blog post once the final release is cut, and docs version change is deployed
  • Publish tweet:
    • Pin new release tweet
    • Confirm with Product if tweet will be promoted
  • Send email in HubSpot
  • Create new notice in Sourcegraph.com global settings 
    "notices": [
  {
    "message": "Sourcegraph {VERSION} is now available! Check out the [{VERSION} release blog post](https://about.sourcegraph.com/blog/sourcegraph-{VERSION}) for more details.",
    "location": "top",
    "dismissible": true
  }
]
  • Use tweet or email content for post on the LinkedIn Sourcegraph company page
  • Put notification in #dev-rel Slack channel with links to blog post and tweet