fix linter issues in enhancements/art
@@ -82,8 +82,9 @@ Enhancement Goal:
will honor the builder images within that Dockerfile until shortly before feature freeze. This
will provide upstream teams:
- Visibility that a change is being recommended.
- - The time to test those changes with full test coverage (not only openshift-tests periodics,
- but also unit, integration, operator tests etc.).
+ - The time to test those changes with full test coverage (not only
+ openshift-tests periodics, but also unit, integration, operator
+ tests etc.).
- The space to align their production metadata if the change is not appropriate for their component.
All before production builds begin to use the suggested change.
- Ensure that all alignment PRs are either merged or closed (after discussion with ART to change
@@ -212,7 +213,8 @@ When analyzing the 4.x-art-latest imagestream, if:
The subsequent entry for a release in is/release would be a union of all istag inconsistency annotations:
`istag/release:4.5.0...` would have the annotation:
-```
+
+```json
'release.openshift.io/inconsistency': {
'tests': [ 'a1', 'a12' ],
'machine-os-content': [ 'a2' ]
@@ -294,5 +296,3 @@ ART equivalent images upstream.
unsupportable (and the architecture team agrees that can be avoided) and then disable them in production
builds (production owners would begin receiving build errors for their component).
2. Fundamentally revisiting internal Red Hat build systems and methods.
-
-
