[bind10-dev] [sprint planning] tentative results and discussion for estimates for sprint ending 2012-12-18

[Jelte Jansen]

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


Ok, so there were quite a few mentions of tickets being either too old
(which need checking to see if they are valid), and being unclear
and/or potentially Big.

Let's first get those out of the way:
#711 (starting to use --user)

As I commented myself in the ticket, behaviour now seems more or less
what could be expected: discover it can't read the config file, and
shut down cleanly. If this is not what it should do, please say so,
otherwise I am inclined to just close it.


#1190 (complete logging conversion for msgq):
ranges from 5 to 100 :) We need to decide what to do and how to
approach it, I suspect this warrants a separate discussion thread
(some ideas are already in the ticket). One other idea could be to
have boss or cfgmgr send a low-level message directly to msgq to
trigger is behaving like any other module (i.e. ask cfgmgr for the
config). Still would be a big task since currently it does not behave
like other modules at all. And of course if we still intend to redo
msgq we might want to wait for that, but in that case we still need to
decide how to approach it.

#1323 (missing zones):
We need to find out if this is is still a problem now that we have a
new interface internally. I am inclined to set it to 1 or 2 just for
doing that check (and then either closing it or setting it to 'new'
again without an estimate)

#2452 (deal with persistent insistence that we have a daemon mode):
This mostly needs figuring out what we want it to do, and as such may
be a non-development task.

#2495 (suggest b10-rndc component):
This needs requirements.

#2509 (extra comma in configuration):
If the case is true that cfgmgr reports FATAL, but then turns zombie,
*that* is a bug to fix. But apart from failing gracefully, I'm not
sure what we could possibly want to do when facing a corrupt JSON file.


Most of the tickets that did get numbers got pretty consistent ones :)

There is one other ticket that may need some discussion/design:

#2515 (dump statistics in DSC-compatible format):
would this require a new 'server' module? or does it fit in either
stats itself or stats-httpd as some option? or should it replace the
xml stats?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlC8lHMACgkQ4nZCKsdOncW0VwCg2if3T3Ha96kXijauulEM0wuj
2/AAn2UTs/M5az4iCBID7zyU8tVtvKSz
=jvK1
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tentative-results-estimates-sprint-20121218.csv
Type: text/csv
Size: 2886 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20121203/21b0f71f/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tentative-results-estimates-sprint-20121218.csv.sig
Type: application/pgp-signature
Size: 72 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20121203/21b0f71f/attachment-0001.bin>