[bind10-dev] A-Team: Task Estimates (planning poker)

[Shane Kerr]

Dear A-Team,

We need some estimates to try to figure out how much work we can do this
sprint. As discussed on the planning call, we don't want to block anyone
waiting on these though. Please proceed with tasks if you are blocking,
trying to pick one that moves us forward.

I haven't created a new web page for the current sprint yet, but either
I'll do that or Stephen will shortly. ;)

It makes sense to use the same basic procedure as the R-Team, which I
shamelessly cut & paste here: 

        A summary of the tasks can be found below: could you please make
        an estimate for each one and send the figures to me.  I will
        collate the numbers and arrange a discussion on the ones for
        which there seems to be wide disagreement.

        As before, the estimate should be one of the following values:

        1, 2, 3, 5, 8, 13, 21, >21 and ?  (? means "no clue")

        When assigning values, compare the tasks with one another.  If
        you feel that task A will take twice as long as task B, assign
        it twice the score of task B, rounding the score up to the
        nearest available value.  (So if you feel that task B should
        have a score of 3, task A should be assigned a score of 8 - the
        next higher allowed value above 2x3 = 6.)

The outstanding tasks on the current page,
http://bind10.isc.org/wiki/ATeam20101201, are here:


Update ZoneTable class to use Red-Black Tree
Documentation on the update to the ZoneTable class
ZoneTable modification and documentation - Review
MemoryZone class
MemoryZone documentation
MemoryZone class and documentation - Review
MemoryZone::load() implementation
MemoryZone::load() documentation
MemoryZone::load() implementation and documentation - Review
MemoryZone::find() implementation
MemoryZone::find() documentation
MemoryZone::find() implementation and documentation - Review
Configuration "knob"
Configuration "knob" documentation
Configuration "knob" implementation and documentation - Review
Implement normal query processing
Document normal query processing
Implement and document normal query processing - Review
Benchmark so we can measure relative performance
Benchmark so we can measure relative performance - Review

There are also these tasks, which come from Jinmei's mail to bind10-dev:

- DB lookup results in NXDOMAIN. simply return SOA in the authority
section
- DB lookup results in NXRRSET (i.e. no error + no answer). simply
  return SOA in the authority section
- zone cut handling in MemoryZone (this may be a bit tricky)
- Delegation processing
- Additional processing for NS
- Additional processing for MX

Thanks!

--
Shane