Jump to: navigation, search

Difference between revisions of "Neutron/ReviewDays"

Line 115: Line 115:
 
| Gary Kotton  
 
| Gary Kotton  
 
|}
 
|}
 +
 +
For Folsom-3, we need to make sure we have two core devs for each key review.  Below is a table with the key community reviews in rough priority order.  Please sign up for the set of reviews that you will continue to revisit until they are merged for F-3. 
 +
 +
Note: if you click through to a review and already seen that two other core devs are active on it, please sign up for other reviews so we can maximize coverage. 
  
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
Line 121: Line 125:
 
|  Review Link  
 
|  Review Link  
 
|  Core Dev #1  
 
|  Core Dev #1  
 +
|-
 +
|  Provider Networks
 +
|  https://review.openstack.org/#/c/10938/
 +
 
|-
 
|-
 
|  RPC support for LB Plugin  
 
|  RPC support for LB Plugin  
Line 130: Line 138:
 
|   
 
|   
 
|-
 
|-
|  Public Networks  
+
|  Public/shared Networks  
 
|  https://review.openstack.org/#/c/9845/  
 
|  https://review.openstack.org/#/c/9845/  
 +
 +
|-
 +
|  L3 + Floating IPs
 +
|  https://review.openstack.org/#/c/10993/
 
|
 
|

Revision as of 01:13, 8 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 */

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.

Day Americas EMEA
Monday July 30th TBA TBA
Tuesday July 31st TBA Salvatore Orlando
Wednesday August 1st Bob Kukura Salvatore Orlando
Thursday August 2nd Sumit Naiksatam TBA
Friday August 3rd Dan Wendlandt Gary Kotton
Saturday August 4th TBA TBA
Sunday August 5th Somik Behera Gary Kotton
Monday August 6th Edgar Magana Gary Kotton
Tuesday August 7th Somik Behera TBA
Wednesday August 8th Bob Kukura TBA
Thursday August 9th Sumit Naiksatam Salvatore Orlando Gary Kotton
Friday August 10th Dan Wendlandt Salvatore Orlando
Saturday August 11th TBA TBA
Sunday August 12th TBA Gary Kotton
Monday August 13th Edgar Magana Salvatore Orlando
Tuesday August 14th Bob Kukura Salvatore Orlando
Wednesday August 15th Dan Wendlandt Gary Kotton
Thursday August 16th TBA Gary Kotton
Friday August 17th Sumit Naiksatam TBA
Saturday August 18th TBA TBA
Sunday August 19th TBA Gary Kotton

For Folsom-3, we need to make sure we have two core devs for each key review. Below is a table with the key community reviews in rough priority order. Please sign up for the set of reviews that you will continue to revisit until they are merged for F-3.

Note: if you click through to a review and already seen that two other core devs are active on it, please sign up for other reviews so we can maximize coverage.

Review Topic Review Link Core Dev #1
Provider Networks https://review.openstack.org/#/c/10938/
RPC support for LB Plugin https://review.openstack.org/#/c/9591/
RPC support for DHCP https://review.openstack.org/#/c/10997/
Public/shared Networks https://review.openstack.org/#/c/9845/
L3 + Floating IPs https://review.openstack.org/#/c/10993/