Patch Review Call: Difference between revisions
From Yocto Project
Jump to navigationJump to search
RossBurton (talk | contribs) (Created page with "We have patch review calls to discuss patches that are under review. Any review comments in the call should be submitted to the mailing list: the list is still the primary location for feedback. There are two meeting times: * Monday, 17:00 - 18:00 UK time * Thursday, 10:00 - 11:00 UK time The intention is to ensure that all patches merged have definitely had multiple eyes looking at them. Future plans: * Move review pipeline from oe-core/master-next to patchwork * Su...") |
RossBurton (talk | contribs) No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
* Monday, 17:00 - 18:00 UK time | * Monday, 17:00 - 18:00 UK time | ||
* Thursday, 10:00 - 11:00 UK time | * Thursday, 10:00 - 11:00 UK time | ||
The calls are held on Zoom at TODO. | |||
The intention is to ensure that all patches merged have definitely had multiple eyes looking at them. | The intention is to ensure that all patches merged have definitely had multiple eyes looking at them, patches that need serious review get assigned to someone, and patches that need further work get replied to on the list. | ||
Future plans: | Future plans: | ||
* Formalise the process further (prior art: the glibc patch review call) | |||
* Move review pipeline from oe-core/master-next to patchwork | * Move review pipeline from oe-core/master-next to patchwork | ||
* | * Tooling: submit autobuilder status to patchwork so b4 can show status | ||
Latest revision as of 17:39, 18 February 2025
We have patch review calls to discuss patches that are under review. Any review comments in the call should be submitted to the mailing list: the list is still the primary location for feedback.
There are two meeting times:
- Monday, 17:00 - 18:00 UK time
- Thursday, 10:00 - 11:00 UK time
The calls are held on Zoom at TODO.
The intention is to ensure that all patches merged have definitely had multiple eyes looking at them, patches that need serious review get assigned to someone, and patches that need further work get replied to on the list.
Future plans:
- Formalise the process further (prior art: the glibc patch review call)
- Move review pipeline from oe-core/master-next to patchwork
- Tooling: submit autobuilder status to patchwork so b4 can show status
