Be more explicit about contingency deadlines
This commit is contained in:
parent
e3664c9e81
commit
ecb7de886c
1 changed files with 5 additions and 1 deletions
|
|
@ -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*
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue