[bind10-dev] R-Team Sprint and Associated Estimates

[Likun Zhang]

I don't give the estimate for the in progress tasks.

> Task List
> =========
> Refactoring: put in library for DNS services
> Wxtracting common code from the authoritative and recursive servers into a
> common library. It was agreed though that this will only be done when all
> branches from ticket #327 have been merged back into that ticket and then
the
> completed ticket merged back into trunk.
Estimate:   ?
Comment: the reason for no clue is: we don't have too much code for
recursive server now, so it means they may don't have too much common code
now. and another, many code used by auth server has been moved to /lib
folder, can the code be used directly by recursive server?


> Merge tickets #393, #401 and #402 back into #327
> These tickets are all branches off #327. They need to be merged back into
it
> before the review can take place.
Estimate:   1


> Review of All Tasks related to #327
> This involves a broad review of the changes made to ticket #327 before it
is
> merged back into trunk.
> Estimate:   3


> Merge #327 back into trunk
> Estimate:   1


> Demux: design phase 1
> The Demux component is the component that matches incoming responses with
> outgoing queries. This is a task for Evan (if we can get him back from
BIND-9 for a
> day) to write down initial thoughts on this.
> Estimate:  5


> Demux: design phase 2
> Expanding Evan's thoughts into a more detailed design.
> Estimate:   3


> Ticket #408: General Control Logic/Logic to Handle NS and A Queries
> This is the framework of the processing described in
> NameserverAddressStoreDesign, and includes the part that actually issues
the
> queries and, when the queries return, updates the data structures and
handles
> the post-processing.
> <In progress>
> Estimate:   ?


> Logic to update RTT
> Definition of the data structures and processing required for the caller
to update
> the RTT associated with nameserver addresses.
> <In progress>
> Estimate:  ?


> Address Selection Logic/RTT Banding
> These tasks have been combined from the previous sprint. This concerns the
> logic needed to select the address with the lowest RTT, yet periodically
try other
> addresses in case their RTT has dropped.
> <In progress>
> Estimate:   ?


> Add basic support for addressing individual list items
> i.e. use [i] in a data structure identifier string to get to the i-th
element (or
> something similar).
> <In progress>
> Estimate:   ?


> Fix bindctl printing of config data
> Currently bindctl tries to be a bit smart (and not too well), and does not
> automatically print the contents of maps or lists unless you specifically
ask for
> that map or list item. That property, combined with the current inability
to
> address individual list items, makes it currently impossible to actually
print out the
> contents of a list that contains maps. So it should be simpler: it should
either print
> out 1 level of data (perhaps the default), or print the full JSON
representation of
> whatever is there.
> <In progress>
> Estimate:   ?


 
> Recursor Cache: Requirements
> Drawing up the requirements for the recursor cache.
> Estimate:  13


> Recursor Cache: API Design
> Design of the API into the cache.
> Estimate:
> Recursor Cache: Test Code
> Writing tests for the cache code.
> Estimate:  13

Comment: My opinion is merge these two tasks together according TDD  


> Outline design for Recursor processing logic
> Produce a design for the processing (primarily based on section 7 of RFC
1035 but
> also including anything from other relevant RFCs). This does not include
DNSSEC
> processing.
> Estimate:  5


> Logging: Requirements
> Drawing up the requirements for BIND-10 logging.
> Estimate:  5


 
> Logging: API Design
> API design for BIND-10 logging. Although it is likely that the logging
will be
> implemented using an existing logging framework, a level of abstraction
will
> make it easier to change the implementation if desired.
> Estimate: 
> Logging: Test Code
> Writing tests for the logging code.
> Estimate:  8

Comment: My opinion is merge these two tasks together according TDD