We release VSCode and JetBrains weekly.

<aside> 💡

Please use pre-release channels for both VS Code (VSCode Insiders) and JetBrains (JetBrains Nightly) to help identify issues before they reach lots of customers.

</aside>

Quick Links

Cody Clients Release Calendar

Cody Clients Release Branching, Tagging and Versions

Release Captain Playbook

Life of a Release

• Engineers land code on main.
• One week before the release, we create a release branch from main. We ship this to VSCode Insiders and JetBrains Nightly channels. Sourcegraph teammates dogfood these builds, QA tests them, and early adopter customers use them. On the release date, provided there are no ship blocking issues, we do the release.
• Each release has a “release captain.” The release captain is responsible for producing a quality release by monitoring issues, coordinating timely fixes, backporting fixes to the release branch, spinning new prerelease builds, and getting QA to test them. This ensures the quality of the next release. Because we fix on main first, it also improves the quality of all subsequent releases.

This process is documented in the Release Captain Playbook.

Because we release weekly, we are continuously monitoring a current stable release, branching and stabilizing the next release, and landing code on main for the next-next release.

For example, using JetBrains version numbers:

When will my PR get released?

After your change lands on main, it will be in the next release branch. It will be available in VSCode Insiders and JetBrains Nightly (used by about 2-5% of our users) soon after the branch. It will be released to stable about one week after that. See the Cody Clients Release Calendar.

Note, customers have control over their own upgrades. Design for old clients talking to new servers and new clients talking to old servers.

I have a critical bug, what should I do?

If you found a critical issue:

1. Notify #discuss-cody or #team-cody-core and tag the release captain, see the Cody Clients Release Calendar.