openinfra/interop
Code Issues Proposed changes

Revert "Update flagging process to include metadata and bug fixes"

Browse Source 
This reverts commit d4e396fa2f68c19624a567db8536a35007513028.

The previous commit adds substantial requirements to the flagging process
and was proposed and merged slightly over 3 hours with only 1 review.  I
have reservations about the additions and strongly feel they need to be
discussed.  Adding them without discussion a few days before we send the
process to the Board for approval is not how we should be making
substantive additions.

Change-Id: If3c928908dd46a73401b21d13d65eaa9ff5d829e
This commit is contained in:
Mark T. Voelker 2015-05-11 00:21:38 +00:00
parent 05fec9169b
commit 2256448222
1 changed files with 0 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
process/2015A.rst
View File

@ -207,20 +207,6 @@ 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 reason, remediation and date:
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