[openstack-dev] [Fuel] Code review process in Fuel and related issues

Igor Kalnitsky ikalnitsky at mirantis.com
Wed Sep 2 12:45:56 UTC 2015


> I think there's plenty of examples of people in OpenStack projects
> that both submit code (and lead features) that also do code review
> on a daily basis.

* Do these features huge?
* Is their code contribution huge or just small patches?
* Did they get to master before FF?
* How many intersecting features OpenStack projects have under
development? (since often merge conflicts requires a lot of re-review)
* How often OpenStack people are busy on other activities, such as
helping fellas, troubleshooting customers, participate design meetings
and so on?

If so, do you sure they are humans then? :) I can only speak for
myself, and that's what I want to say: during 7.0 dev cycle I burned
in hell and I don't want to continue that way.

Thanks,
Igor

On Wed, Sep 2, 2015 at 3:14 PM, Jay Pipes <jaypipes at gmail.com> wrote:
> On 09/02/2015 03:00 AM, Igor Kalnitsky wrote:
>>
>> It won't work that way. You either busy on writing code / leading
>> feature or doing review. It couldn't be combined effectively. Any
>> context switch between activities requires an extra time to focus on.
>
>
> I don't agree with the above, Igor. I think there's plenty of examples of
> people in OpenStack projects that both submit code (and lead features) that
> also do code review on a daily basis.
>
> Best,
> -jay
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



More information about the OpenStack-dev mailing list