Difference between revisions of "Neutron/ReviewDays"

Revision as of 15:44, 28 August 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

/* end */

Folsom RC Special Review Guidelines

• only spend core review cycles on items that are assigned to Folsom RC1: https://launchpad.net/quantum/+milestone/folsom-rc1
• on your review day, also triage any new quantum bugs to identify any that may need to apply to RC1. Focus on triaging all bugs in 'New' state, moving them to 'confirmed', 'invalid', or 'incomplete', and assigning them a priority. See BugTriage for more details. If anything is unclear discuss it with PTL.

See People for mappings between real names and IRC handles.