...
- Every POC has a named sponsor for the feature whom acts as spokesperson at all checkpoints/meetings
- POC (only) related defects cannot block the release
- POC development that includes entry points in the release version must comply with license scans and vulnerability fixes
- A POC should not introduce a back-door to the stable features so it must comply with security, code coverage, and license scans requirements
- POC features that are visible/accessible in the final product should be documented with limitations and POC status stated
- A use case POC using common code, does not change the treatment of the common code with regards to completeness, S3P, documentation and other common code expectations
- Otherwise, POC should be kept in separate repo branch
==-=-=-=-=-=-=-=-=-=-=-CUT LINE, Previous content preserved for continuity... Delete after TSC review-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
...