[bind10-dev] [sprint planning] tentative results + discussion for estimates for sprint ending 2013-something

[Jelte Jansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Don't be scared of the long list below; for most the estimates didn't
actually vary that much, but these tickets may or may not warrant some
discussion or explanation

Jelte


#2558 (fromJSON is not able to handle full uint32 range):
minor point (range from 1-5); this appears to only need review

#2556 (output from bind10 (when Resolver shutdown)):
ranges from not estimated to 8; details are a bit fuzzy, but it looks
like a linker problem (and hence should in theory be resolved by clean
build/install and/or updating the library version before release). But
we should confirm this.

#2552 (log output has two spaces after INFO):
This is currently kind of intended behaviour; the format we set
explicitely makes this happen (not just INFO, WARN as well). It is
easy to change, but the question is, is easier output for split/cut
more important than aligning the output?

#2538 (Explain the format and purpose of ZoneTableSegment::create
config parameter):
Most estimates are 2/3 but one is 8; from the ticket I gather that
this is just a bit of API documentation, are we wrong?

#2550 (logging stdout fallback includes debug even without -v):
Estimates range from 2 to 8; This has some discussion in the ticket
that caused it, and it is potentially more tricky than it appears. One
obvious solution will have a drawback itself (no DEBUG output for
initial messages even if config is set to DEBUG but -v is NOT given).
We *think* that there may be a reasonably easy solution if the log
system is initialized in a slightly different way, but if not, it can
get a bit tricky.

#2511 (defining a data_sources/classes/IN disables the builtin CH):
This is probably 'solvable' through better documentation; the specific
command isn't shown in the ticket but it looks like this is intended
behaviour (if you 'set' the entire thing in one command then it'll
replace any existing data, and hence remove things)

#2279 (requirements for configuration framework improvements):
Estimates range from 3 to 13. It is 'just' requirements, but we should
probably make it around 8 anyway, as these can be tricky to get right
(And should have quite a bit of discussion)

#2073 (unified way to define zones with attributes):
This probably needs a more specific ideas or proposals, and may be
related to the config framework requirements (in the sense that those
may offer some support for config abstraction).

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDO9tEACgkQ4nZCKsdOncWMwgCePhwiZe1TKag2f2Vca/3Pv11b
LZoAnRm5FcrtIy09+m/OZFjYWUnuGXSx
=Wo7f
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tentative-results-estimates-sprint-20130101.csv
Type: text/csv
Size: 2627 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20121217/060c9bd7/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tentative-results-estimates-sprint-20130101.csv.sig
Type: application/pgp-signature
Size: 72 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20121217/060c9bd7/attachment-0001.bin>