[bind10-dev] code reviews

[JINMEI Tatuya / 神明達哉]

At Fri, 16 Apr 2010 15:56:56 -0500,
Michael Graff <mgraff at isc.org> wrote:

> I'll admit I've not read too far into what you wrote here.  However, I'm
> worried we are getting too process-centric on this, and process-centric
> is somewhat anti-Agile.  Actually it's sometimes very anti-Agile...

I expected this response:-) But to be clear, it was not my intent to
propose the constitution of development.  I simply tried to clarify
what we're "basically" expected to do in more specific way.  The
actual operation can be flexible, relying on our common sense.

> I think any of us developers, or ones we hire, can manage to decide if
> the change is one of these things:
> 
>   Is the change big?
> 
>   Is the change functional?
> 
>   Is the change likely to be controversial?
> 
> If it is any of the above, it is likely grounds for review.  If it is
> none of them, or the change was discussed in-depth with others, then it
> might be ok to let it through without review.

I have one quick question.  If it needs a review on the other hand,
what should we do?  That's actually my main concern in this
discussion.  In the strawman idea I proposed to use a short-lived
branch for this purpose.

---
JINMEI, Tatuya