fleet-release
fleet-release
Check for vulnerabilities on the production dependencies of fleetdm.com. > Read more at https://fleetdm.com/handbook/digital-experience#check-production-dependencies-of-fleetdm-com
Check for vulnerabilities on the production dependencies of fleetdm.com. > Read more at https://fleetdm.com/handbook/digital-experience#check-production-dependencies-of-fleetdm-com
Use Browserstack to manually QA pages on fleetdm.com in each of the earliest supported browser versions > Read more at https://fleetdm.com/handbook/digital-experience#check-browser-compatibility-for-fleetdm-com
Check for vulnerabilities on the production dependencies of fleetdm.com. > Read more at https://fleetdm.com/handbook/digital-experience#check-production-dependencies-of-fleetdm-com
Every quarter, Head of Product Design (HPD) meets with the CEO to run through the current quarter objectives and the 3 biggest open opportunities in the product and the solutions...
Use Browserstack to manually QA pages on fleetdm.com in each of the earliest supported browser versions > Read more at https://fleetdm.com/handbook/digital-experience#check-browser-compatibility-for-fleetdm-com
Check the osquery Slack invitation that is linked to from Fleet and the Fleet website to make sure it is valid. > Read more at https://fleetdm.com/slack
Check for vulnerabilities on the production dependencies of fleetdm.com. > Read more at https://fleetdm.com/handbook/digital-experience#check-production-dependencies-of-fleetdm-com
After a release documentation PR is merged to `main`, merge the latest from `main` into each upcoming release docs branch.
1. Close any draft PRs (to auto-generated docs) for released features. 2. Prepare documentation PR to `main`. 3. @-mention release DRI