Lines Matching full:2
26 2. All the GitHub Actions pass and the PR is ready to be reviewed.
27 2. Triage
29 2. The assignee assigns a reviewer from the FreeRTOS Team to the PR.
32 …2. If the contributor and the reviewer conclude, after discussion, that the PR will not be merged,…
37 2. The PR contributor addresses the feedback and makes changes to the PR, if needed.
43 1. At least 2 reviews.
44 2. One review from the CODEOWNER of the given repository.
53 …ot go through all the above stages, however every PR is required to get approvals from 2 reviewers.
67 * Concept ACK/NACK: 1-2 weeks
68 * Code Review: 1-2 weeks
69 * Testing: 1-2 weeks
86 2. Smaller is better. Small, focused PR’s are reviewed more quickly and thoroughly, are simpler to …