From e64827f0517a4bf199bad252cc52ecd913e7f06b Mon Sep 17 00:00:00 2001 From: Christian Ehrhardt Date: Fri, 7 Jul 2023 08:03:16 +0200 Subject: [PATCH] special HW, clarify section H We want to be sure people see that this provides details to the access outlined above. Based on the suggestion in review this also suggests details on when/where any regular tests migth be triggered. Signed-off-by: Christian Ehrhardt --- README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 5c07ca5bb2..439c1f16d3 100644 --- a/README.md +++ b/README.md @@ -319,11 +319,12 @@ TODO-G: - We have engaged with our user community and due to that TODO-G: can tests new package builds via TBD TODO-H: - We have engaged with the hardware manufacturer and made an TODO-H: agreement to test new builds via TBD -TODO-A-H: - Here are the details of the test plan/automation TBD (e.g. script -TODO-A-H: or repo) and (if possible) example output of a test run TBD (logs). -TODO-A-H: We will execute that +TODO-A-H: - Based on that access outlined above, here are the details of the +TODO-A-H: test plan/automation TBD (e.g. script or repo) and (if already +TODO-A-H: possible) example output of a test run: TBD (logs). +TODO-A-H: We will execute that test plan TODO-A-H1: on-uploads -TODO-A-H2: regularly +TODO-A-H2: regularly (TBD details like frequency: monthly, infra: jira-url) TODO-X: - We have exhausted all options, there really is no feasible way TODO-X: to test or recreate this. We are aware of the extra implications TODO-X: and duties this has for our team (= help SEG and security on