From ecb7de886c747e2f8888b88c92c7b2472c95cca1 Mon Sep 17 00:00:00 2001 From: Ben Cotton Date: Thu, 24 Jun 2021 09:24:39 -0400 Subject: [PATCH] Be more explicit about contingency deadlines --- modules/ROOT/pages/changes_guide.adoc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/changes_guide.adoc b/modules/ROOT/pages/changes_guide.adoc index 78d6e70..0c6ce13 100644 --- a/modules/ROOT/pages/changes_guide.adoc +++ b/modules/ROOT/pages/changes_guide.adoc @@ -178,7 +178,11 @@ If you feature is not completed in time we want to assure others that other part A contigency plan should include: * Contingency mechanism: (What to do? Who will do it?) -* Contingency deadline: When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. +* Contingency deadline: When is the last time the contingency mechanism can be put in place? + +TIP: The contingency deadline will most likely be the beta freeze. +In some cases, it may be more appropriate to set it to the start of the mass rebuild or branch day. +Rarely, you can use final freeze, but this should only be used for Changes that are trivially-revertable. === Documentation *REQUIRED FOR SYSTEM-WIDE CHANGES*