[bind10-dev] memo for the A team planning meeting

[JINMEI Tatuya / 神明達哉]

Pretty unreadable, but I thought brain dump might be helpful
especially because I'll be sleeping until the meeting...

A. Observations
- we were still too optimistic about estimation.  Of 18 tasks (which
  could have been completed and merged to trunk in the ideal world),
  only 2 were completed; 7 ongoing (progress varies); 9 haven't
  started.
- we did some non planned tasks.  since A team is very small, we
  should probably focus on the sprint tasks more.
- to make the result "reasonably workable", we need at least 6 more
  new tasks.  (looks like quite impossible to complete in the next
  sprint...)

B. Task Status

(based on my memo sent after the previous planning meeting, merging
dev+doc tasks.  There's also a wiki page:
http://bind10.isc.org/wiki/ATeam20101201?version=18)

Done (merged to trunk) 
1. complete outstanding review and merge: #415
2. complete outstanding review and merge: #418
(note: review was done by Jelte, that is, we needed help outside of
the team)

At least first development is completed, but review/merge isn't:
3. complete the necessary stuff of RBT.
7. implement MemoryDataSrc class. (+ documentation)
9. review and merge of task #7.
10. A simple (master) zone file parser. (+ documentation)
12. review and merge of task #10.

Started but development isn't completed:
22. configuration knob (+ documentation)

Ongoing review
15. review and merge of task #14.

Non planned tasks
- review the statistics branch
- xfrout bug fix
- build error fixes due to nsas merge
- travel

Not started:
4. update to the ZoneTable class (+ documentation)
6. review and merge of task #4
16. MemoryZone::load() implementation (+ documentation)
18. review and merge of task #16.
19. MemoryZone::find() implementation (+ documentation)
21. review and merge of task #19.
24. review and merge of task #22.
25. implement normal query processing (+ documentation)
27. review and merge of task #25.
- (optional) performance measurement
  The resulting performance at this point is not so important (and
  even if it's not good yet we shouldn't jump into optimization now),
  but if we (someone) have time measuring it may be interesting.

C. Future tasks

Query processing logic (continued, from the design memo, should be
more broken down later)
- 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

We also need to heavily improve the rbt documentation.

---
JINMEI, Tatuya