Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

Remove duplicate section (#38808)

Browse source
This commit is contained in:
Luke Heath 2026-01-26 14:12:19 -06:00 committed by GitHub
parent 686a1cfe65
commit 604f04a8c3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 0 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
handbook/engineering/README.md
View file

@ -163,20 +163,6 @@ Mitigating the outage may require writing and merging code. The current infrastr
> If outside of business hours, the responding engineer should notify their manager using incident.io to bypass Do Not Disturb mode.
### Create a release candidate
Fleet responds to all P0 incidents by initiating our incident response process:
1. Create a new incident response issue in our confidential repo.
2. Edit the issue template to reflect the details of the incident.
3. Assign to the on-call engineer that received the incident for initial triage, as well as the current infrastrucure on-call engineer.
4. Complete the steps listed based on the type of incident.
Mitigating the outage may require writing and merging code. The current infrastructure on-call engineer is first line for all reviews and QA required to deploy a hot-fix. If additional code review or engineering support is needed, the responding engineer should escalate to their manager.
> If outside of business hours, the responding engineer should notify their manager using incident.io to bypass Do Not Disturb mode.
### Create a release candidate
All minor releases go through the release candidate process before they are published. A release candidate for the next minor release is created on the last Friday of each sprint at 8:00 AM Pacific (see [Fleet's release calendar](https://calendar.google.com/calendar/u/0?cid=Y192Nzk0M2RlcW4xdW5zNDg4YTY1djJkOTRic0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t)). A release candidate branch is created at `rc-minor-fleet-v4.x.x` and no additional feature work or released bug fixes are merged without EM and QA approval.