- the code is "in the process of" getting a cleanup.  there are still a
  few globally scoped variables that ought to be removed and/or replaced
  by local scoped variables.

- testing various corner cases:
  - errors dumping during upgrade
  - errors dumping during purge

- multiple instance support for many databases from one package.  the
  idea is to create seperate "package configurations" that are derived
  from the main configuration, using something to keep them in a namespace
  that won't conflict with the standard package configurations.  something
  like /etc/dbconfig-common/package_instance.conf etc.  most of dbconfig's
  code could escape needing a rewrite then, as we could internally "trick"
  the code into thinking that was the actual package name.

- provide a normal-user-accessible script for setting up databases
  (for running out of public_html type directories etc).

- think about how this should tie in with the webapps-common.

- begin discussion on having the "best-practices" document incorporated
  in some form as debian policy.

- ask if the user is to be completely deleted or only have privileges
  revoked in mysql.  this is the default in pgsql, but in pgsql the drop
  will fail if the user owns other databases (not so in mysql).
  See bug #400566

- mysql does not support ssl for the time being (see bug #291945) <- fixed...

- bug 556174 might need additional logic to ask if the debian-sys-maint is
  allowed to be used (as it only works on local systems). Maybe try first and
  only ask upon failure. Probably just works if /etc/mysql/debian.cnf exists.

- Biggest bug: should check if mysql is actually running during upgrade
  706512, but probably also 579319 and maybe more

- FIX no-admin patch to use new VAR instead of debconf item (to prevent
   regression test from failing)

- Think about how mariadb needs to be supported

*  Fix postinst to use _dbc_asuser when appropriate   
   
*  Add testcase that tests admin remove scripts (#705222)

*  Switch to shorthand dh

*  Update examples to debhelper 9 (shorthand)

*  Swith package structure to dbconfig-<dbtype>

*  debconf is not a registry should not lead to dbconfig-common has its own
   registry (which is currently the case)

*  Provide config parsers (as requested in 690390(?) against debconf)

*  Get dbconfig-common mentioned in policy

*  Remove some of the upgrade code if no package depends on it make things easier

*  Improve first dbconfig-common question to:
   - warn against cornercases -> don't use dbconfig-common then
   - mention the server side packages (should be easier with splitted dbconfig)

*  More databases (e.g. mongodb)

*  Support DSN: apperently python has multiple ways of making the connection

*  Rumors have it that the default way to connect to mariadb is like "postgresql"
   ident.

*  Postgresql renamed ident to peer (I should ask Christoph)
