[bind10-dev] BIND 10: Y2 intermediate releases milestones (proposal)
Shane Kerr
shane at isc.org
Thu May 27 12:56:51 UTC 2010
All,
Our 6-month milestones are on the Wiki here:
https://bind10.isc.org/wiki/Year2Milestones
I have been told to do more work defining the intermediate milestones,
so here I go.
After the release next week, I propose 3 more releases in the first half
of Y2, on the following dates:
2010-07-01
2010-08-12
2010-09-17
For each release, I propose the following intermediate milestones:
2010-07-01: The Cha-Cha-Changes to the Data Source Release
We implement a writable data source! Also, we begin our
optimization work and our recursive work.
* Implement the read/write data source API in C++ for SQLite
* Document how stats are collected (ticket #170), plus begin
implementation (ticket #191)
* Publish the documentation guidelines for each module
* Benchmarks
* Authoritative benchmarks setup & published automatically
* Recursive benchmark setup designed & implementation
begun
* Profiling automated & set up
* Recursive architecture & design
* Benchmark passing packets between processes
* Dispatch (BIND 9 sense) implemented
* Design DNS cache
* Python logging framework implemented, used by some modules
* msgq: JSON conversion
* Secondary Manager
* PrivilegedSocket
2010-08-12: The I Can't Believe It's Not SQLite3 Release
Our first non-SQLite3 back end: Berkeley Database.
* Berkeley Database data source
* Improve the read/write data source, plus implement the Python
API
* Add tests to get 80% coverage for all modules
* Python logging framework used by all modules
* C++ logging framework implemented, used by some modules
* Recursive server: document classes & interactions
* Optimize hot-spot caching
2010-09-17:
Our first "major" milestone: Y2 after 6 months!
* xfrin and loadzone use read/write data source
* Publish statistics via bindctl
* All modules documented according to our guidelines
* All modules using logging framework
* Bug fixes
The July release is much heavier than the following two - we'll need to
discuss what actually goes in the release on our 2010-07-06 conference
call, since these goals may be a bit aggressive. I intentionally put
more work at the beginning so that if we need to push something it won't
go past our 6-month milestone!
This doesn't cover everything - we'll need to make some decisions about
whether caching will give us enough performance or if we need an
in-memory database for example, and we need to think about IXFR and
DDNS, and we need to look at the Python 2 vs. Python 3 issue, but these
bullet points hopefully cover the important tasks.
Anyway, please comment on-list, and we will discuss it in a couple of
weeks.
--
Shane
More information about the bind10-dev
mailing list