Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I/O PR Review Policy Proposal #4934

Closed
patrickhulce opened this issue Apr 5, 2018 · 4 comments
Closed

I/O PR Review Policy Proposal #4934

patrickhulce opened this issue Apr 5, 2018 · 4 comments

Comments

@patrickhulce
Copy link
Collaborator

patrickhulce commented Apr 5, 2018

This is a proposal to introduce a new PR label: "I/O-Expedite". Any PR with this label will have certain expectations around review timelines before it can just be merged without explicit approval. The goal of this is to ensure v3 priorities have proper chance for review while still enabling us to meet I/O timelines.

When a PR is first labelled as "I/O-Expedite", each member of core team has 8 working hours1 to give their initial review. After feedback has been addressed and the author requests re-review, the reviewers have 4 working hours to request more changes.

A priority PR can be merged when Travis is green and one of the following conditions have been met:

  • All reviewers2 approve
  • 8 working hours have elapsed without any feedback
  • 4 working hours have elapsed since addressing/responding to all feedback3 without further reviewer2 comments

1 = M-F 10am-6pm PST
2 = A reviewer is any person who provides feedback within the initial 8 working hour window
3 = notice must be given in PR that feedback has been addressed and PR is ready for re-review

@patrickhulce
Copy link
Collaborator Author

@paulirish @brendankenny this SG?

@paulirish
Copy link
Member

M-F 9am-6pm PST

10-6? :)

After feedback has been addressed and the author requests re-review, the reviewers have 4 working hours to request more changes.

Is this just for a re-review whether its approval or not?

@patrickhulce
Copy link
Collaborator Author

10-6? :)

ya :)

Is this just for a re-review whether its approval or not?

Not 100% I understand the question, but I intended that sentence to mean that once an author has replied to all comments/made all requested changes, the reviewer has 4 hours to get back to them before the author is allowed to assume that the reviewer has given their approval :) If the reviewer gets back to them with more requested changes, then the clock resets

@paulirish
Copy link
Member

It was a success.

Thanks @patrickhulce and also for everyone's participation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants