From c3b1d1e6ba37d41052e89ab0ad9e6d02819830b3 Mon Sep 17 00:00:00 2001 From: robhirschfeld Date: Tue, 28 Jul 2015 11:58:47 -0500 Subject: [PATCH] As per 2015.07 discussion, new Guidelines should not start with flag tests in new guidelines. This HACKING rule will ensure that all tests in guidelines are added by intent and not accidently carried from the next.json file. Change-Id: I11ab2ec8f0f79fe4c0f114d61eed35b1d7f318dc --- HACKING.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/HACKING.rst b/HACKING.rst index 3606710b..f3d076eb 100644 --- a/HACKING.rst +++ b/HACKING.rst @@ -79,7 +79,8 @@ DefCore Specific Commandments #. The DefCore committee will discuss and consider the flagging proposal as well as the proposed new reason. They may accept or decline either proposal. - [D311] Once a test has been flaged, it will remain flagged for that Guideline. - +- [D312] When a new guideline is proposed for Board approval, no flagged tests + will be included in the guideline. Flags will be added in subsequent patches. DefCore Test Flagging Guidelines --------------------------------