I originally didn't add a changelog entry for it as I originally
thought was too trivial (change package name in single place in
configure.ac).

Discussed via jabber.

Conflicts:
	src/bin/dhcp4/dhcp4_messages.mes

Without this header the build fails on CentOS as it does not recognize
uint32_t type.

from bind10-devel to bind10

instead of bind10-devel

also increase the version to today's date stamp (not for "beta")

The cppcheck seems to have difficulty to figure out that the variable is
set and initialized within a loop and that it is read within another
loop iteration.

Merge of #2380 missed a couple of cases, and added a few more sleeps to help with background loading checks.

using tools/reorder_message_file.py to reorder

mention some defaults

Remove sendstats and document getstats.

Document internal start_ddns_forwarder and stop_ddns_forwarder.

Add extra SEE ALSO.

Okayed via jabber.

both discussed on jabber (today and yesterday)

This fixes the omission in previous commit.

Conflicts:
	ChangeLog
	src/lib/dhcpsrv/alloc_engine.cc

this is necessary for distcheck.

it can take time without any feedback while deleting old zone data,
so it's probably better to note that explicitly.

this seems to be the actual intent of the RFC, and it's compatible with
BIND 9, too.  This fix will resolve the remaining regression for the
old loadzone tests.

see the log for the previous commit for the rationale.

test parameters were adjusted accordingly.
there are some non trivial adjustments needed for the 'correct' test
cases for the original loadzone:
- completing the origin for some RDATA paramaeters (NS, SOA) does not
  work yet until we complete the RDATA support.  At the moment
  I made them FQDNs with comments
- a few TXT data were actually incorrect in the original tests, which
  caused a seeming regression.  I fixed the test data.
- there was one real bug in the $INCLUDE + origin support.  I'll go
  fix it; right now it fails

The 'error' test cases for the original loadzone also fail, but overall
the intended behavior looked preserved.  Fixing the tests to make it pass
seems to be quite difficult (because log output are different, and
the new loadzone ng is more verbose), so I plan to simply remove these
tests.

Value stored to 'opt_len' during its initialization is never read

discussed via jabber

also use const