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

sandbox-oncall -> infrastructure-oncall and fix old channel names (#9969)

Browse source 
# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] Added/updated tests
- [ ] Manual QA for all new/changed functionality
  - For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).
This commit is contained in:
Zachary Winnerman 2023-02-21 07:11:50 -05:00 committed by GitHub
parent 02d21dd495
commit 765a43cb50
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/Contributing/Releasing-Fleet.md
View file

@ -93,7 +93,7 @@ Note: Please prefix versions with `fleet-v` (e.g., `fleet-v4.0.0`) in git tags,
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.
6. In the #g-customer-experience Slack channel, notify the @infrastructure-oncall of the release. This way, the @infrastructure-oncall individual can deploy the new version.
7. Announce the release in the #fleet channel of [osquery
Slack](https://fleetdm.com/slack) and

4
handbook/engineering/README.md
View file

@ -889,7 +889,7 @@ Escalations (in order):
- Zach Wasserman
The first responder oncall will take ownership of the @sandbox-oncall alias in Slack for ease first thing Monday morning.
The first responder oncall will take ownership of the @infrastructure-oncall alias in Slack for ease first thing Monday morning.
Expected response times: during business hours, 1 hour. Outside of business hours 4 hours.
@ -899,7 +899,7 @@ We should collect both the email for the customer and information for the error.
Escalation of issues will be done by hand for the moment.
All infrastructure alarms will go to #g-infrastructure.
All infrastructure alarms will go to #help-p1.
The information needed to evaluate and potentially fix any issues is documented in the [runbook](https://github.com/fleetdm/fleet/blob/main/infrastructure/sandbox/readme.md).