Lines Matching full:review

6 Code Review
31 Give reviewers time to review before code merge
36 changes are proposed using pull request, we need to allow for a minimal review
37 time to give developers and contributors the opportunity to review and comment
42 code-owner review. Additionally, some changes might require further discussions
44 the diagram below proposes minimal review times for each category:
75 on the fix, severity, and availability of someone to review them (other than the
76 author) they can be merged with justification without review by one of the
129 Pull Request should not be merged by author without review
133 without a review. The following exceptions apply:
139 Developers and contributors should always seek review, however there are cases
148 that a change should not be merged without their review, then: Request change
177 - The review is unrelated to the code change or asking for unjustified
205 through review and build testing to verify doc generation will be successful.
207 Any failures found during the CI test run will result in a negative review
327      - Simple changes that can have shorter review time and be reviewed by anyone, i.e. typos,
331      - Maintainer review required.
333    * - :guilabel:`Security Review`
340    * - :guilabel:`Needs review`
347      - The PR has licensing issues which require a licensing expert to review it.
352    review. See :ref:`review process <review_time>` for details.
376    * - :guilabel:`dev-review`
377      - The issue is to be discussed in the following `dev-review`_ if time
380 ….. _`dev-review`: https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-G…