Difference between revisions of "Neutron/ReviewDays"

Revision as of 02:37, 11 July 2012

We are thinking about having an assigned reviewer for each day.

Review duty rotates between every (human) member of quantum-core. If you are the assigned reviewer, it's your responsibility to: /* start */

• Set blueprint proposals to "Approved" if appropriate, or request more information.
• Review patches.
• Assign domain experts to patches withouth a review. In this case the domain expert might be or might not be a core dev. In the latter case a core dev should probably be selected as well for the branch.
• Respond to queries from contributors concerning pending reviews or blueprint approvals.
• Pester assigned reviewers to review branches.

/* end */

Active reviews for trunk: https://review.openstack.org/#q,status:open+project:openstack/quantum,n,z

Every human member of quantum-core should be part of this rotation. As we have core developers in several we will try to leverage this as much as possible. For this reason, the table below has 3 columns corresponding to 3 different time "areas": Americas, EMEA, and APAC.

Approximately a core reviewer would be available in the following hours: /* start */

• APAC: 1AM GMT - 9AM GMT
• EMEA: 9AM GMT - 5PM GMT
• Americas: 5PM GMT - 1AM GMT

Th /* end */

It would be great if we could fill every column for each day, but having just one reviewer on duty in a given time area 4 days out of 5 would probably be an acceptable result. The idea is to start this scheme on Monday June 18th, and Update this schedule every 2 weeks, in order to accomodate as much as possible for holydays or other things.

See People for mappings between real names and IRC handles.