@@ -11,7 +11,7 @@ Credentials for various services used in this process can be found in 1Password.
Use the `releases` Slack channel to notify the team that releases will be starting.
This is mostly a formality on Wednesday's minor update releases, but can be beneficial when doing patch releases, as other devs may have landed fixes they'd like to cherry pick.
----
+### Starting the Builds
1. Checkout `main` and ensure your working copy is clean.
@@ -19,44 +19,74 @@ This is mostly a formality on Wednesday's minor update releases, but can be bene
1. Run `git fetch --tags --force` to forcibly ensure your local tags are in sync with the remote.
-1. Run `./script/get-stable-channel-release-notes`.
-
- - Follow the instructions at the end of the script and aggregate the release notes into one structure.
+1. Run `./script/get-stable-channel-release-notes` and store output locally.
1. Run `./script/bump-zed-minor-versions`.
- Push the tags and branches as instructed.
-1. Run `./script/get-preview-channel-changes`.
+1. Run `./script/get-preview-channel-changes` and store output locally.
- - Take the script's output and build release notes by organizing each release note line into a category.
- - Use a prior release for the initial outline.
- - Make sure to append the `Credit` line, if present, to the end of the release note line.
+> **Note:** Always prioritize the stable release.
+> If you've completed aggregating stable release notes, you can move on to working on aggregating preview release notes, but once the stable build has finished, work through the rest of the stable steps to fully publish.
+> Preview can be finished up after.
-1. Once release drafts are up on [GitHub Releases](https://github.com/zed-industries/zed/releases), paste both preview and stable release notes into each and **save**.
+### Stable Release
- - **Do not publish the drafts!**
+1. Aggregate stable release notes.
-1. Check the release assets.
+ - Follow the instructions at the end of the script and aggregate the release notes into one structure.
- - Ensure the stable and preview release jobs have finished without error.
- - Ensure each draft has the proper number of assets—releases currently have 11 assets each.
- - Download the artifacts for each release draft and test that you can run them locally.
+1. Once the stable release draft is up on [GitHub Releases](https://github.com/zed-industries/zed/releases), paste the stable release notes into it and **save**.
+
+ - **Do not publish the draft!**
+
+1. Check the stable release assets.
-1. Publish the drafts.
+ - Ensure the stable release job has finished without error.
+ - Ensure the draft has the proper number of assets—releases currently have 11 assets each.
+ - Download the artifacts for the stable release draft and test that you can run them locally.
- - Publish stable and preview drafts, one at a time.
- - Use [Vercel](https://vercel.com/zed-industries/zed-dev) to check the progress of the website rebuild.
- The release will be public once the rebuild has completed.
+1. Publish the stable draft on [GitHub Releases](https://github.com/zed-industries/zed/releases).
+
+ - Use [Vercel](https://vercel.com/zed-industries/zed-dev) to check the progress of the website rebuild.
+ The release will be public once the rebuild has completed.
1. Post the stable release notes to social media.
- Bluesky and X posts will already be built as drafts in [Buffer](https://buffer.com).
+ - Double-check links.
- Publish both, one at a time, ensuring both are posted to each respective platform.
1. Send the stable release notes email.
- The email broadcast will already be built as a draft in [Kit](https://kit.com).
+ - Double-check links.
+ - Publish the email.
+
+### Preview Release
+
+1. Aggregate preview release notes.
+
+ - Take the script's output and build release notes by organizing each release note line into a category.
+ - Use a prior release for the initial outline.
+ - Make sure to append the `Credit` line, if present, to the end of the release note line.
+
+1. Once the preview release draft is up on [GitHub Releases](https://github.com/zed-industries/zed/releases), paste the preview release notes into it and **save**.
+
+ - **Do not publish the draft!**
+
+1. Check the preview release assets.
+
+ - Ensure the preview release job has finished without error.
+ - Ensure the draft has the proper number of assets—releases currently have 11 assets each.
+ - Download the artifacts for the preview release draft and test that you can run them locally.
+
+1. Publish the preview draft on [GitHub Releases](https://github.com/zed-industries/zed/releases).
+ - Use [Vercel](https://vercel.com/zed-industries/zed-dev) to check the progress of the website rebuild.
+ The release will be public once the rebuild has completed.
+
+### Prep Content for Next Week's Stable Release
1. Build social media posts based on the popular items in preview.