mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 08:58:41 +00:00
Document 0-day macOS major version support process beginning with macOS 16 (#22243)
Co-authored-by: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com>
This commit is contained in:
parent
90c04eef37
commit
e2ac27e011
1 changed files with 13 additions and 1 deletions
|
|
@ -538,13 +538,25 @@ Upon receiving any device, follow these steps to process incoming equipment.
|
|||
Once the Digital Experience department approves inventory to be shipped from Fleet IT, follow these step to ship the equipment.
|
||||
1. Compare the equipment request issue with the ["Company equipment" spreadsheet](https://docs.google.com/spreadsheets/d/1hFlymLlRWIaWeVh14IRz03yE-ytBLfUaqVz0VVmmoGI/edit#gid=0) and verify physical inventory.
|
||||
2. Plug in the device and ensure inventory has been correctly processed and all components are present (e.g. charger cord, power converter).
|
||||
3. package equipment for shipment and include Yubikeys (if requested).
|
||||
3. Package equipment for shipment and include Yubikeys (if requested).
|
||||
4. Change the "Company equipment" spreadsheet to reflect the new user.
|
||||
- If you encounter any issues, repeat the [process incoming equipment steps](https://fleetdm.com/handbook/engineering#process-incoming-equipment). If problems persist, create a ["💻 IT support issue](https://github.com/fleetdm/confidential/issues/new?assignees=%40spokanemac&labels=%3Ahelp-it&projects=&template=request-it-support.md&title=%F0%9F%92%BB+Request+IT+support) for IT to troubleshoot the device.
|
||||
6. Ship via FedEx to the address listed in the equipment request.
|
||||
7. Add a comment to the equipment request issue, at-mentioning the requestor with the FedEx tracking info and close the issue.
|
||||
|
||||
|
||||
### Provide 0-day support for major version macOS releases
|
||||
|
||||
Beginning with macOS 16, Fleet will offer 0-day support for all major version macOS releases.
|
||||
|
||||
1. Install major version macOS beta release on test devices.
|
||||
2. Create a new [QA release issue](https://github.com/fleetdm/fleet/issues/new?assignees=xpkoala%2Cpezhub&labels=%23g-mdm%2C%23g-endpoint-ops%2C%3Arelease&projects=&template=release-qa.md&title=Release+QA%3A+macOS+16) with the new major version in the issue title.
|
||||
3. Complete all manual smoke tests in the issue and confirm they are passing.
|
||||
4. Confirm all automated tests are passing.
|
||||
5. [File bugs](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=P1%2Cbug%2C%3Areproduce%2C%3Aincoming&projects=&template=bug-report.md&title=) with a `P1` label and assign to the appropriate [product group](https://fleetdm.com/handbook/company/product-groups#current-product-groups).
|
||||
6. When all bugs are fixed, follow the [writing a feature guide](https://fleetdm.com/handbook/engineering#write-a-feature-guide) process to publish an article announcing Fleet 0-day support for the new major release.
|
||||
|
||||
|
||||
## Rituals
|
||||
|
||||
<rituals :rituals="rituals['handbook/engineering/engineering.rituals.yml']"></rituals>
|
||||
|
|
|
|||
Loading…
Reference in a new issue