From 9970ac668bdb0fd6c6736e50415962ffaa1bc4a8 Mon Sep 17 00:00:00 2001 From: Eric Date: Thu, 6 Oct 2022 11:04:36 -0500 Subject: [PATCH] Docs: add missing `pageOrderInSection` meta tag (#8104) * Update Orbit-development-and-release-strategy.md * Update docs/Contributing/Orbit-development-and-release-strategy.md Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com> Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com> --- docs/Contributing/Orbit-development-and-release-strategy.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/Contributing/Orbit-development-and-release-strategy.md b/docs/Contributing/Orbit-development-and-release-strategy.md index 024b406b5a..544615da73 100644 --- a/docs/Contributing/Orbit-development-and-release-strategy.md +++ b/docs/Contributing/Orbit-development-and-release-strategy.md @@ -27,4 +27,6 @@ This allows some flexibility when developing new features in Orbit and Fleet. ## Release process 1. Orbit components (Orbit itself, Fleet Desktop and osqueryd) must be released to FleetDM's TUF before new Fleet server releases are available in Github. -2. When the new Fleet server version doesn't support older Orbit versions (see [Nice to have](#nice-to-have)), the release notes must document their minimum supported Orbit version. This is for users that use Orbit with auto-updates disabled or they pin to a specific channel. These users would need to first update Orbit in their devices, and then proceed to upgrade Fleet server. \ No newline at end of file +2. When the new Fleet server version doesn't support older Orbit versions (see [Nice to have](#nice-to-have)), the release notes must document their minimum supported Orbit version. This is for users that use Orbit with auto-updates disabled or they pin to a specific channel. These users would need to first update Orbit in their devices and then proceed to upgrade Fleet server. + + \ No newline at end of file