-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write usage guide for the scheduled maintenance feature #20763
Comments
@sharon-fdm I realized we don't have a guide for the scheduled maintenance feature. We'll need to write and publish one before we release 4.55, so I'm creating this P2 release blocker to track the request. Please estimate this and assign out. We have a specific process for writing these using a template. Instructions for writing a usage guide are here: https://github.com/fleetdm/fleet/pull/20668/files. Will be in the engineering handbook soon. Thanks! |
@sharon-fdm - Said he'll talk to @lukeheath about updating the reference AND/OR creating a guide as described above |
@getvictor recording 7/31 incoming |
@RachelElysia, as agreed, we will do both a Guide and update the ref doc. |
@getvictor please review the document when you can. |
Hey @lukeheath! I'm going over issues in confirm and celebrate column and I noticed that we decided to hold the guide: #20974 (comment) What do you think we should do with this issue? We could leave it in confirm and celebrate until we're ready to ship the guide. I think we could also ship the guide. I'm not sure why we want to wait for OS updates improvement. We don't mention OS updates in the guide: https://github.com/fleetdm/fleet/pull/20974/files |
@noahtalerman I think we have to hold it in confirm and celebrate so we don't forget to come back and publish it. Mike asked us to remove all scheduled maintenance content until we're confident in the OS upgrade workflow. |
Goal
Instructions for writing a usage guide are here: https://github.com/fleetdm/fleet/pull/20668/files
Context
Related tickets
The text was updated successfully, but these errors were encountered: