openinfra/interop
Code Issues Proposed changes

As per 2015.07 discussion, new Guidelines should not start with flag tests

Browse Source 
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
This commit is contained in:
robhirschfeld 2015-07-28 11:58:47 -05:00
parent cc3ad916b7
commit c3b1d1e6ba
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
HACKING.rst
View File

@ -79,7 +79,8 @@ DefCore Specific Commandments
#. The DefCore committee will discuss and consider the flagging proposal as #. The DefCore committee will discuss and consider the flagging proposal as
well as the proposed new reason. They may accept or decline either proposal. 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. - [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 DefCore Test Flagging Guidelines
-------------------------------- --------------------------------