From e5e2fe7965f7230387f0ee2ce34b46926e7abd3b Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Thu, 13 Oct 2022 11:32:01 -0400
Subject: [PATCH] Add 2 steps to the "Releasing Fleet" process (#8101)

- Add a "Deploy to dogfood" step
- Add a "Notify the @sandbox-oncall" step
---
 docs/Contributing/Releasing-Fleet.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/docs/Contributing/Releasing-Fleet.md b/docs/Contributing/Releasing-Fleet.md
index a09716deb6..7889034a11 100644
--- a/docs/Contributing/Releasing-Fleet.md
+++ b/docs/Contributing/Releasing-Fleet.md
@@ -91,7 +91,11 @@ Note: Please prefix versions with `fleet-v` (e.g., `fleet-v4.0.0`) in git tags,
 > publish a prerelease of fleetctl while the most recent fleetctl npm package, available for public
 > download, is still the latest _official_ release.
 
-5. Announce the release in the #fleet channel of [osquery
+5. Deploy the new version to Fleet's internal dogfood instance: https://fleetdm.com/handbook/engineering#deploying-to-dogfood.
+
+6. In the #g-infrastructure Slack channel, notify the @sandbox-oncall of the release. This way, the @sandbox-oncall individual can deploy the new version.
+
+7. Announce the release in the #fleet channel of [osquery
    Slack](https://fleetdm.com/slack) and
    update the channel's topic with the link to this release. Using `@here` requires admin
    permissions, so typically this announcement will be done by `@zwass`.