BIND 10 #2308: [meta] beta ticket

[BIND 10 Development]

#2308: [meta] beta ticket
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:  task   |                Status:  new
                   Priority:         |             Milestone:  New Tasks
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  Core
                   Keywords:         |  Estimated Difficulty:  meta
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Description changed by jreed:

Old description:

> This ticket is to track other tickets toward the first production
> release. (As discussed on
> http://bind10.isc.org/wiki/WeeklyMinutes20121003 -- actually one day
> earlier.) Add ticket numbers as needed for the following:
>
> - #2368 complete and generic zone file parser and loader
>
> - UI improvements? need refactoring/rewriting of internal code there
>
> - #2256 SQL database backend
>
> - BIND 9/10 configuration interoperability
>
> - docs: how to run unittests and lettuce tests (we don't release lettuces
> tests currently, they are only in repos)
>
> - #2305 bindctl documentation
>             also document that bindctl is a low-level interface and that
> we plan a more intuitive simple interface too?
>
> - Upgrade docs (how to restart)
>
> - document what is not "production quality"
>
> - document if dhcp is supported, or where should be used (and how)
>
> - #2306 document "execute"
>
> - #2307 perfdhcp manual
>
> - quick start guide --  update it
>
> - system/architecture documentation (not user) -- need to decide
>
> - versions for components -- remove them? or update them
>         currently we just ignore the versions
>         what are the values of the separate versions?
>         if just is a release version, confusing to bump for no reason (if
> no code changed)
>         if do ship independently, having versions may or may not be good
>         bump all versions?
>         ask the list (the would be users) ...
>
> - #2255 get rid of multiple data source configurations (also see #2261)
>
> - #1351 get rid of multiple TSIG configurations (also see #2262)
>
> - #1044 ssl cert generation
>
> - #1622 logging still in multiple files after rotation
>         document we need a certain log4cplus minimum version? configure
> abort or complain if old version?
>
> - #1190 output or logging from msgq;
>     maybe stick in separate log file?
>
> - get rid of any asserts during shutdown
>
> - #1049 get rid of kill -9 during shutdown
>
> - #1858 sockcreator still running (after bind10 not running) or hanging
>
> - #2367 select features to build and install
>
> - consistent naming, like Auth or auth or b10-auth; and plugin spec files
> that don't match feature names; boss or Boss or "bind10".

New description:

 This ticket is to track other tickets toward the first production release.
 (As discussed on http://bind10.isc.org/wiki/WeeklyMinutes20121003 --
 actually one day earlier.) Add ticket numbers as needed for the following:

 - #2368 complete and generic zone file parser and loader

 - UI improvements? need refactoring/rewriting of internal code there

 - #2256 SQL database backend

 - BIND 9/10 configuration interoperability

 - docs: how to run unittests and more about lettuce tests (we don't
 release lettuces tests currently, they are only in repos); see #2341

 - #2305 bindctl documentation
             also document that bindctl is a low-level interface and that
 we plan a more intuitive simple interface too?

 - Upgrade docs (how to restart)

 - document what is not "production quality"

 - document if dhcp is supported, or where should be used (and how)

 - #2306 document "execute"

 - #2307 perfdhcp manual

 - quick start guide --  update it

 - system/architecture documentation (not user) -- need to decide

 - versions for components -- remove them? or update them
         currently we just ignore the versions
         what are the values of the separate versions?
         if just is a release version, confusing to bump for no reason (if
 no code changed)
         if do ship independently, having versions may or may not be good
         bump all versions?
         ask the list (the would be users) ...

 - #2255 get rid of multiple data source configurations (also see #2261)

 - #1351 get rid of multiple TSIG configurations (also see #2262)

 - #1044 ssl cert generation

 - #1622 logging still in multiple files after rotation
         document we need a certain log4cplus minimum version? configure
 abort or complain if old version?

 - #1190 output or logging from msgq;
     maybe stick in separate log file?

 - get rid of any asserts during shutdown

 - #1049 get rid of kill -9 during shutdown

 - #1858 sockcreator still running (after bind10 not running) or hanging

 - #2367 select features to build and install

 - consistent naming, like Auth or auth or b10-auth; and plugin spec files
 that don't match feature names; boss or Boss or "bind10".

--

-- 
Ticket URL: <http://bind10.isc.org/ticket/2308#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development