Lines Matching full:changes
71 merging a pull request. However, Contributors comments and requested changes
87 * Responsibility to review relevant code changes within reasonable time.
176 * Right to merge code changes to the zephyr tree following the project rules.
177 * Right to revert any changes that have broken the code base
178 * Right to close any stale changes after <N> months of no activity
223 verify changes either directly or through QA before major
224 changes and major milestones.
277 in a standalone commit alongside other changes introducing new files and
279 * Major changes to the file, including the addition of new areas with new maintainers
282 should send the requested changes to the TSC and give members of the TSC two
283 (2) days to object to any of the changes to maintainership of areas or the
285 * Path, collaborator and name changes do not require a review by the TSC.
319 each affected area; Unless the changes to a given area are considered trivial
328 * Changes or additions to common and shared code shall have approvals from
333 * Changes or additions to hardware support (driver, SoC, boards) shall at
342 * Release engineers shall not merge code changes originating and reviewed
343 only by their own organisation. To be able to merge such changes, at least
346 * A minimum review period of 2 business days, 4 hours for trivial changes (see