From 9c2b4679be6d5055eb0b2c0da8420cf115f2b874 Mon Sep 17 00:00:00 2001 From: Jussi Kukkonen Date: Wed, 19 Jun 2024 13:29:35 +0300 Subject: [PATCH] docs: Make suggested review fixes to migration doc Signed-off-by: Jussi Kukkonen --- docs/migration/README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/migration/README.md b/docs/migration/README.md index ecb253cd..40feea63 100644 --- a/docs/migration/README.md +++ b/docs/migration/README.md @@ -7,7 +7,7 @@ tuf-on-ci actions. ## Summary -Roughly he migration steps are +Roughly the migration steps are 1. Prepare the GitHub project, workflows, cloud services and the data _without disrupting the current operations_ 2. Run the initial signing event with tuf-on-ci, do the necessary changes to metadata _without disrupting @@ -23,6 +23,9 @@ the online signing machinery will modify metadata every three days. Within that * Decide the signing event was not successful and restart step 2 at a later date or * complete steps 2 and 3 +The deadline can be extended by a couple of days (as the actual expiry period is ~7 days) but this requires +additional communication with on-call. + ## Detailed playbook ### 1. Preparation @@ -66,7 +69,8 @@ This playbook and manuals for signers and maintainers. #### Signer orientation -Make sure signers have installed and tested the software, and understand what will be requested during the signing event +Make sure signers have installed and tested the software, and understand what will be requested during the signing +event -- especially with regards ~3 day timeline to evaluate and make a go/no-go decision. #### General outreach