-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
7
-
None
-
None
-
OTA 272, OTA 273, OTA 274
I hear that folks want something similar to the OpenShift API conditions:
- Tests must contain either [OCPFeatureGate:<FeatureGateName>] or the standard upstream [FeatureGate:<FeatureGateName>].
- There must be at least five tests for each FeatureGate.
- Every test must be run on every TechPreview platform we have jobs for. (Ask for an exception if your feature doesn't support a variant.)
...
before promoting command-line features to GA. Or maybe that is a condition before shifting them from alpha to beta, like this upstream change moving a commend-line gate from IsEnabled to !IsDisabled?
Definition of done: enough test-cases running somewhere that the Technical Release Team would approve promoting some portion of the recommend subcommand to GA.
- blocks
-
OTA-1560 Drop some feature gate environment variables from the 'recommend' subcommand
-
- Closed
-
- is blocked by
-
OCPBUGS-60877 'oc adm inspect-alerts' and relatives should respect --certificate-authority
-
- Verified
-
- is cloned by
-
OCPBUGS-61062 'oc adm upgrade recommend' alert/accept test-cases to satisfy the tech-preview-to-GA transition
-
- Closed
-
- links to