[bind10-dev] statistics plan

[JINMEI Tatuya / 神明達哉]

At Wed, 22 Aug 2012 20:28:54 +0900 (JST),
Naoki Kambe <kambe at jprs.co.jp> wrote:

> Regarding the next 2 sprints, can we plan to include these statistics
> tickets into the following sprints?
> 
>   Tickets included into the next sprint ending in Sep. 04 are:
>     #2136, #2138, #2179, #2154, #2155, and #2157
> 
>   Tickets included into the sprint ending in Sep. 18 after the next
>   are:
>     #2156, #2158, and taken-over tickets (if there are)
> 
> Further, can we plan to start reviewing on each ticket within 2
> working days after it's ready for reviewing?  And then, can we plan to
> give review comments on each ticket within 5 working days after
> reviewing is started?

I think the short answer is "it's best effort basis".  Starting review
within a couple of days should normally be the case based on our basic
policy of prioritizing review requests.  But the issue for the
statistics tickets is that reviewers and developers are different, and
from reviewers' point of view the review tasks of statistics tickets
are an addition to the development and review of non-statistics
tasks.  So, realistically, I'm afraid we cannot really guarantee when
to start the review.  I hope we all understand this fact, but if the
delay exceeds the acceptable range even considering it, you can push
the request harder in daily calls.

Once the review starts, I guess it's reasonable to assume it's
completed within 5 days.  I'd say even that's pretty long; we
generally want to keep tasks small enough so both development and
review should be done within a couple of days.  (But of course, it
primarily depends on whether each statistics ticket is reasonably
small).

(not specific to statistics tickets, it may be a good idea to collect
statistics about the duration of completing a ticket and use it for
planning).

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.