[bind10-dev] DHCP code sharing in BIND 10

[Jeremy C. Reed]

On Mon, 30 May 2011, Tomasz Mrugalski wrote:

> DHCP in BIND10 work is slowly getting started. It's a good time to think
> about workflow - how should DHCP work be organized to not interfere with
> BIND10 DNS. You can finid my initial proposal here:
> 
> http://bind10.isc.org/wiki/DhcpWorkflow
> 
> I'd like to ask for your comments and ideas.


It has for DHCP and BIND 10 DNS to release at same time: "cons: none?" 
The overhead for doing a release includes documentation, functional 
testing, review of important defect tickets, release notes, etc. So a 
negative is to do more work at a single time versus spreading the work 
out. Nevertheless, I think a single release is best.

We had discussed long ago having separate releases for different 
components as they matured, since some may have active development while 
others may simply be stable with little development.

Will you clarify your "Proposed modules" list on the wiki page to 
identify what is a library/python module versus a daemon? Also what do 
you imagine will be first coded in C++ or in Python (or other)?

Some other things to consider as part of the workflow:

- Who will do code reviews?

- Use of existing build/test farm systems? use of existing buildfarm 
software? If using existing build farm, responsibilities include 
following up quickly for introduced failures/regressions by helping fix 
problems and/or backing out changes. Also coordination with making sure 
software dependencies are installed and making sure unit 
tests/functional tests can run independently with simultaneous 
builds/tests.  (I imagine that an advanced test farm will be needed for 
failover testing and to provide numerous DHCP client types also. Maybe 
existing ISC DHCP's test farm may be used, but I don't know about it.)

- Who will do API and end-user documentation: writing, editing, 
generation in various formats, etc? (For the DNS side, the developers 
generally write their own API documentation using pydoc and Doxygen 
formats so docs are embedded as comments within code.)