Jump to: navigation, search

Difference between revisions of "Neutron/ReviewDays"

Line 38: Line 38:
 
| Tuesday August 21st  
 
| Tuesday August 21st  
 
|   
 
|   
|   
+
Gary Kotton
 
|-
 
|-
 
| Wednesday August 22nd  
 
| Wednesday August 22nd  
 
|   
 
|   
|   
+
Gary Kotton
 
|-
 
|-
 
| Thursday August 23rd  
 
| Thursday August 23rd  
Line 58: Line 58:
 
| Sunday August 26th  
 
| Sunday August 26th  
 
|   
 
|   
|   
+
Gary Kotton
 
|-
 
|-
 
| Monday August 27th  
 
| Monday August 27th  
 
|   
 
|   
|   
+
Gary Kotton
 
|-
 
|-
 
| Tuesday August 28th  
 
| Tuesday August 28th  
 
|   
 
|   
|   
+
Gary Kotton
 
|-
 
|-
 
| Wednesday August 29th  
 
| Wednesday August 29th  
Line 86: Line 86:
 
| Sunday September 2nd  
 
| Sunday September 2nd  
 
|   
 
|   
|   
+
Gary Kotton
 
|-
 
|-
 
| Monday September 3rd  
 
| Monday September 3rd  
|   
+
Gary Kotton
 
|   
 
|   
 
|-
 
|-
Line 98: Line 98:
 
| Wednesday September 5th  
 
| Wednesday September 5th  
 
|   
 
|   
|   
+
Gary Kotton
 
|-
 
|-
 
| Thursday September 6th  
 
| Thursday September 6th  
Line 114: Line 114:
 
| Sunday September 9th
 
| Sunday September 9th
 
|   
 
|   
|
+
| Gary Kotton

Revision as of 06:56, 21 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 August 20th Salvatore Orlando
Tuesday August 21st Gary Kotton
Wednesday August 22nd Gary Kotton
Thursday August 23rd Dan Wendlandt Salvatore Orlando
Friday August 24th Sumit Naiksatam
Saturday August 25th
Sunday August 26th Gary Kotton
Monday August 27th Gary Kotton
Tuesday August 28th Gary Kotton
Wednesday August 29th
Thursday August 30th Dan Wendlandt Salvatore Orlando
Friday August 31st Sumit Naiksatam Salvatore Orlando
Saturday September 1st
Sunday September 2nd Gary Kotton
Monday September 3rd Gary Kotton
Tuesday September 4th Salvatore Orlando
Wednesday September 5th Gary Kotton
Thursday September 6th Dan Wendlandt Salvatore Orlando
Friday September 7th Sumit Naiksatam
Saturday September 8th
Sunday September 9th Gary Kotton