Design docs: Clarify how verifications should be
Inspired-By: David Pursehouse <dpursehouse@collab.net>
Change-Id: Ia2b0cd5456c2db1adfb4731aca01982fba4c01a8
diff --git a/Documentation/dev-design-docs.txt b/Documentation/dev-design-docs.txt
index 20ee979..be80c94 100644
--- a/Documentation/dev-design-docs.txt
+++ b/Documentation/dev-design-docs.txt
@@ -107,6 +107,10 @@
comment threads stop there and do not clutter the current review. It is up
to the alternative reviews to then host their related comments.
+Verification should be based on the generated `jekyll` site using the
+local `docker`, rather than via the rendering in `gitiles` (via
+`gerrit-review`).
+
Changes which make a conclusion on a design (changes that add/change
the `conclusion.md` file, see link:#structure[Design Doc Structure])
should stay open for a minimum of 10 calendar days so that everyone has
