This page is a “how to” guide for being Cody Core release captain.

Key Responsibilities

• At the start of a new release, create the release branch.
• Stabilize the release branch by triaging issues and backporting fixes.
• Prev release captain would take care of patch release of the current release ($MILESTONE_MINUS_TWO).
• At the end of the prerelease period, create the stable release.
• (The following week) Patch releases after this week’s release is out ($MILESTONE).
• Prev release captain would take care of patch release of the current release ($MILESTONE_MINUS_TWO).

Prerequisites

• Clone github.com/sourcegraph/cody.git and have write access to it.
• Set up a JetBrains account(with your sourcegraph email). Then, check if you have admin access by visiting https://plugins.jetbrains.com/vendor/sourcegraph/edit. If you don't have admin access, post a request in #team-cody-core to be added to the JetBrains Marketplace team.
• Set up the GitHub CLI.
• Read Cody Clients Release Branching, Tagging and Versions so you can name branches and tags correctly. Automation is triggered by names matching exactly.

<aside> 💡

This page shows commands as if you are release captain for VSCode 1.66 and JetBrains 7.66. As you use the playbook, substitute versions that are right for you. 🫵

(We tried writing it more abstractly but it just makes it twice as long and half as clear.)

</aside>

Day 1: Create a release branch

Confirm the details of your release by checking the release calendar:

• Branch date. We typically branch every Wednesday PM US Pacific time, but we may move a release date to avoid a holiday/match a Sourcegraph release/etc.
• Release version and branch names. These are in the release calendar.

Check that the previous release captain has produced the stable VSCode release. They should have dropped a message in #team-cody-core.