Update flagging process to include metadata and bug fixes
Updates the flagging process to require vendors to include flag metadata for reason, remediation steps, and date of flagging. Also updates process to require vendors to attempt to fix bugs in tests and upstream code where reasonably possible before submitting flagged test lists. Change-Id: I72e57e3a9643daa712dce938a9baba3c8ce4c898
This commit is contained in:
parent
5aad0eccf1
commit
d4e396fa2f
@ -207,6 +207,18 @@ C3. Vendor Grievance Process
|
||||
3. The DefCore committee will acknowledge vendor requests to flag tests
|
||||
within 30 days.
|
||||
4. Vendors may not request flagging all tests in a capability.
|
||||
5. Tests marked for flagging must include:
|
||||
a. A reason for the flag, which may include but is not limited to
|
||||
a capability not being widely supported or an existing bug
|
||||
in the test.
|
||||
b. A remediation step to remove the flag. Options include removing
|
||||
the test from the next release, fixing an existing feature in
|
||||
upstream code, or fixing the bug in the test suite.
|
||||
c. A date of test flagging to give guidance to the committee for
|
||||
future test removal.
|
||||
6. Vendors must make a good-faith effort to document the reason for
|
||||
flagging, and where possible attempt to fix upstream bugs in test
|
||||
or production code before submitting tests for flagging.
|
||||
|
||||
C4. Results of Vendor Self-Tests will be open
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user