[bind10-dev] statistics plan

[Naoki Kambe]

Hello,

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?

In case of #2179, for example, can we start reviewing by Aug. 24, and
can we give review comments by Aug. 31?

Can that make sense?

Best regards,

Naoki Kambe


From: JINMEI Tatuya / 神明達哉 <jinmei at isc.org>
Subject: Re: [bind10-dev] statistics plan
Date: Tue, 21 Aug 2012 23:38:33 -0700

> At Tue, 21 Aug 2012 19:02:12 +0900 (JST),
> Naoki Kambe <kambe at jprs.co.jp> wrote:
> 
> > Regarding these prioritized statistics tickets, JPRS would like to know
> > approximate dates as the followings:
> > 
> >  - When a reviewer will be assigned to
> >  - When reviewing will be started
> >  - When reviewing will be finished
> 
> I think these will be considered in the context of normal sprint
> planning.
> 
> > >   "must be done" (scheduled to end until Aug21)：
> > >     #2136 update the stats daemon according to the new statistics model
> > in reviewing
> > >     #2137 update the boss module according to the new statistics model
> > almost done (waiting for merging of #2136)
> > >     #2138 update the Auth module according to the new statistics model
> > in reviewing
> > >     #2179 Update Stats to support differential statistics updates
> > ready for reviewing
> 
> All of the above are in the current sprint.  So basically, the answer
> to the questions for these is "by the end of this sprint".  Of course,
> as is the case for other tickets in a sprint, the plan is not always
> fully met, and that actually seems to be happening for these tickets
> too.
> 
> > >   "optional" (scheduled to end until Sep18)：
> > >     #2154 Create a set of counters to hold auth statistics items
> > ready for reviewing
> > >     #2155 Collect query/response statistics items in Auth module
> > ready for reviewing
> > >     #2157 Create an interface to pass statistics counters in Auth module
> > ready for reviewing
> > >     #2156 Collect socket statistics items in Auth module
> > accepted
> > >     #2158 Implement counters into Xfrout (1/3)
> > accepted
> 
> With our current pace, I guess half of them will be included in the
> next sprint (~Sep4), and the rest will be in the next to it (~Sep18).
> Realistically, I suspect it's less likely we'll fully complete (=
> merged to master) all of them by September 18.  I believe "must be
> done" items will be pretty likely to be merged, and I guess we should
> prioritize things in the "optional" ones.
> 
> ---
> JINMEI, Tatuya
> Internet Systems Consortium, Inc.
>