-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
cnv-virtctl-tech-debt
-
False
-
-
False
-
- Code in pkg/virtctl meets the criteria defined in the upstream coding conventions
- Code in pkg/virtctl is covered by unit tests as best as possible
- Code in pkg/virtctl passes linters
- Open bugs are fixed
-
None
-
In Progress
-
54% To Do, 12% In Progress, 35% Done
-
Yes
Tech debt stories leftover from previous virtctl epics
Goal
The kubevirt/kubevirt code base would benefit from having owners of dedicated areas.
User Stories
- As a developer I want a clean code struct, so that it is a joy to add new feature and to fix bugs.
- As a developer I want all functional tests to pass without flakes, so that the build would pass all gates, so that upstream CI is reliable passing and the downstream builds are delivered to stakeholders without delay.
Non-Requirements
- Functional or UX improvements are nice to have.
Notes
- Any additional details or decisions made/needed
