Lines Matching refs:changes

72 and requested changes should still be considered by the pull request author.
89 * Responsibility to review relevant code changes within reasonable time.
101 be addressed by the original submitter. In cases where the changes requested do
173 * Right to block pull requests from being merged until issues or changes
215 * Right to merge code changes to the zephyr tree following the project rules.
216 * Right to revert any changes that have broken the code base
217 * Right to close any stale changes after <N> months of no activity
262   verify changes either directly or through QA before major
263   changes and major milestones.
313   in a standalone commit alongside other changes introducing new files and
315 * Major changes to the file, including the addition of new areas with new maintainers
318   should send the requested changes to the TSC and give members of the TSC two
319   (2) days to object to any of the changes to maintainership of areas or the
321 * Path, collaborator and name changes do not require a review by the TSC.
355   each affected area; Unless the changes to a given area are considered trivial
378   * Release engineers shall not merge code changes originating and reviewed
379     only by their own organisation. To be able to merge such changes, at least
382 * A minimum review period of 2 business days, 4 hours for trivial changes (see