[openstack-dev] [nova] [neutron] Gerrit spec reviews
Hi Nova developers: I have a question around the new nova-specs gerrit repository. We're implementing the same thing in Neutron for Juno (I'm hoping to make this live tomorrow), but I had a few quick questions so I can build on your experience with this so far: 1. Did you implement any sort of time limit on BPs in review? Mostly around trying to triage the BPs as they come in. 2. Nova has a subset of the core-team which can actually approve BPs, is this correct? 3. For all BPs submitted using the new procedure, is it required to submit a Summit session? Any guidance appreciated here! Thanks, Kyle ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [neutron] Gerrit spec reviews
This page actually has most of the answers on it: https://wiki.openstack.org/wiki/Blueprints#Nova 1: The time limit is one release: at the end of each release, non-completed specs will be removed 2: The nova-drivers team approves specs 3: No, it's not required to have a summit session. Something like that would be problematic, as blueprints could be proposed after summit. Hope that helps. IMHO, the nova-specs gerrit repository is a great way to review blueprints. I'm really liking it so far. Best Regards, Solly Ross - Original Message - From: Kyle Mestery mest...@noironetworks.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Tuesday, April 15, 2014 5:14:14 PM Subject: [openstack-dev] [nova] [neutron] Gerrit spec reviews Hi Nova developers: I have a question around the new nova-specs gerrit repository. We're implementing the same thing in Neutron for Juno (I'm hoping to make this live tomorrow), but I had a few quick questions so I can build on your experience with this so far: 1. Did you implement any sort of time limit on BPs in review? Mostly around trying to triage the BPs as they come in. 2. Nova has a subset of the core-team which can actually approve BPs, is this correct? 3. For all BPs submitted using the new procedure, is it required to submit a Summit session? Any guidance appreciated here! Thanks, Kyle ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [neutron] Gerrit spec reviews
On 04/15/2014 05:14 PM, Kyle Mestery wrote: Hi Nova developers: I have a question around the new nova-specs gerrit repository. We're implementing the same thing in Neutron for Juno (I'm hoping to make this live tomorrow), but I had a few quick questions so I can build on your experience with this so far: 1. Did you implement any sort of time limit on BPs in review? Mostly around trying to triage the BPs as they come in. No limits yet other than the organic limits of how fast we can get through them. 2. Nova has a subset of the core-team which can actually approve BPs, is this correct? Correct. The team is nova-drivers [1]. This is the team that assisted me with the blueprint review process last cycle, as well. My plan was to continue to manage the team sort of like we manage nova-core: update with new members after they gained trust from the others after demonstrating dedication and high review quality. Going forward, I defer to the Juno PTL on any changes that may be made here. 3. For all BPs submitted using the new procedure, is it required to submit a Summit session? No. More details of the process on [2]. [1] https://launchpad.net/~nova-drivers/+members#active [2] https://wiki.openstack.org/wiki/Blueprints#Creation -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [neutron] Gerrit spec reviews
Thanks Solly, and I agree on the benefits here, which is why Neutron is moving to the same process as Nova for these BP reviews. Thanks, Kyle On Tue, Apr 15, 2014 at 4:24 PM, Solly Ross sr...@redhat.com wrote: This page actually has most of the answers on it: https://wiki.openstack.org/wiki/Blueprints#Nova 1: The time limit is one release: at the end of each release, non-completed specs will be removed 2: The nova-drivers team approves specs 3: No, it's not required to have a summit session. Something like that would be problematic, as blueprints could be proposed after summit. Hope that helps. IMHO, the nova-specs gerrit repository is a great way to review blueprints. I'm really liking it so far. Best Regards, Solly Ross - Original Message - From: Kyle Mestery mest...@noironetworks.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Tuesday, April 15, 2014 5:14:14 PM Subject: [openstack-dev] [nova] [neutron] Gerrit spec reviews Hi Nova developers: I have a question around the new nova-specs gerrit repository. We're implementing the same thing in Neutron for Juno (I'm hoping to make this live tomorrow), but I had a few quick questions so I can build on your experience with this so far: 1. Did you implement any sort of time limit on BPs in review? Mostly around trying to triage the BPs as they come in. 2. Nova has a subset of the core-team which can actually approve BPs, is this correct? 3. For all BPs submitted using the new procedure, is it required to submit a Summit session? Any guidance appreciated here! Thanks, Kyle ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [neutron] Gerrit spec reviews
On Wed, Apr 16, 2014 at 7:31 AM, Russell Bryant rbry...@redhat.com wrote: On 04/15/2014 05:14 PM, Kyle Mestery wrote: 2. Nova has a subset of the core-team which can actually approve BPs, is this correct? Correct. The team is nova-drivers [1]. This is the team that assisted me with the blueprint review process last cycle, as well. My plan was to continue to manage the team sort of like we manage nova-core: update with new members after they gained trust from the others after demonstrating dedication and high review quality. Going forward, I defer to the Juno PTL on any changes that may be made here. I agree with this plan. I also think that given nova-specs is so new, the first couple of iterations of updates to nova-drivers might be quite rapid. We probably have enough data already to know who is engaging with this process and isn't part of nova-drivers. That will drive the first update to nova-drivers. Michael -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
