Skip to content

Commit

Permalink
Clarify when message should be sent
Browse files Browse the repository at this point in the history
  • Loading branch information
ppawlowski committed Jan 24, 2025
1 parent d0739c1 commit a3f4b18
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion src/handbook/development/ops/maintenance.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,9 @@ E-mail template for maintenance communication can be found in the [FlowFuse Clou

The notification message should be sent to all FlowFuse Cloud Team Owners who have active instances in the FlowFuse Cloud. To get the contact list, please refere to the [internal documentation](https://docs.google.com/document/d/1s0mXpuuPKl-1U-YVzoTEGBhllUd-UPJjFXTqa0O481c/#heading=h.hing87m0bsmu).

Before sending the message, consult with the Operations team to ensure that the information is up-to-date and infrastructure is ready to handle self-care maintenance by customers.
We should sent notification at least twice - two weeks before the maintenance and a reminder one week before the maintenance day.

Before sending the initial message, consult with the Operations team to ensure that the information is up-to-date and infrastructure is ready to handle self-care maintenance by customers.

## Infrastructure preparation

Expand Down

0 comments on commit a3f4b18

Please sign in to comment.