Jump to: navigation, search

Difference between revisions of "Neutron/ReviewDays"

Line 34: Line 34:
 
|  EMEA  
 
|  EMEA  
 
|-
 
|-
|rowspan="2" | Monday June 18th   
+
| Monday June 18th   
 
|  TBA   
 
|  TBA   
 
|  TBA  
 
|  TBA  
 
|-
 
|-
|rowspan="2" | Tuesday June 19th
+
| Tuesday June 19th  
 
|  TBA  
 
|  TBA  
 
|  TBA  
 
|  TBA  
 
|-
 
|-
|rowspan="2" | Wednesday June 20th  
+
| Wednesday June 20th  
 
|  TBA  
 
|  TBA  
 
|  TBA  
 
|  TBA  
 
|-
 
|-
 +
| Thursday June 21st 
 +
|  TBA
 +
|  TBA
 
|-
 
|-
|rowspan="2" | Thursday June 21st  
+
| Friday June 22nd
 +
|  TBA
 +
TBA
 
|-
 
|-
 +
| Monday June 25th
 +
|  TBA
 +
|  TBA
 
|-
 
|-
|rowspan="2" | Friday June 22nd   
+
| Tuesday June 26th
 +
| TBA
 +
|  [[SalvatoreOrlando]]
 
|-
 
|-
 +
| Wednesday June 27th
 +
|  TBA
 +
|  TBA
 
|-
 
|-
|rowspan="2" | Monday June 25th   
+
| Thursday June 28th
 +
| TBA
 +
|  TBA
 
|-
 
|-
|-
+
| Friday June 29th
|rowspan="2" | Tuesday June 26th   
+
| TBA
|-
+
TBA
|-
 
|rowspan="2" | Wednesday June 27th  
 
|-
 
|-
 
|rowspan="2" | Thursday June 28th 
 
|-
 
|-
 
|rowspan="2" | Friday June 29th
 

Revision as of 11:18, 11 June 2012

We have decided to have 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 */

  • Americas: 5PM GMT - 1AM GMT
  • EMEA: 9AM GMT - 5PM GMT
  • APAC: 1AM GMT - 9AM 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 June 18th TBA TBA
Tuesday June 19th TBA TBA
Wednesday June 20th TBA TBA
Thursday June 21st TBA TBA
Friday June 22nd TBA TBA
Monday June 25th TBA TBA
Tuesday June 26th TBA SalvatoreOrlando
Wednesday June 27th TBA TBA
Thursday June 28th TBA TBA
Friday June 29th TBA TBA