-
Epic
-
Resolution: Done
-
Major
-
None
-
upstream-coding-conventions
-
77
-
- coding guideline document is merged
- coding guideline document is accepted by all kv/kv approvers
-
To Do
-
CNV-38613 - 2024 Code Quality
-
-
0% To Do, 0% In Progress, 100% Done
-
dev-ready, doc-ready, po-ready, qe-ready, ux-ready
Goal
Establish coding conventions in upstream KubeVirt in order to ensure that we are creating maintainable code.
https://github.com/kubevirt/kubevirt/issues/11259 is a good starting point.
User Stories
- As a developers, I am aware of the expectations of the approvers, so that I can prepare my PR to match the expectations.
- As an approve, I can reference the coding guidelines in my reviews, so that it is transparent that code code review is based on agreed guidelines.
Non-Requirements
- The checking of the coding guideline is done manually by the approvers, there is no autoatic checking.
- The coding guidelines has to be accepted by the approvers of https://github.com/kubevirt/kubevirt , the acceptance of approves of other repositories is optional.
Notes
- Any additional details or decisions made/needed
1.
|
upstream roadmap issue |
|
Closed | |
Unassigned |
2.
|
upstream design |
|
Closed | |
Unassigned |
3.
|
upstream documentation |
|
Closed | |
Unassigned |
4.
|
upgrade consideration |
|
Closed | |
Unassigned |
5.
|
CEE/PX summary presentation |
|
Closed | |
Unassigned |
6.
|
test plans in polarion |
|
Closed | |
Unassigned |
7.
|
automated tests |
|
Closed | |
Unassigned |
8.
|
downstream documentation merged |
|
Closed | |
Unassigned |