how to find what features/options added between releases?

[Jeremy C. Reed]

I am trying to compile a list of the features and options added (and maybe 
removed or syntax changed) between the 9.2.x, 9.3.x, 9.4.x, and HEAD. (My 
list is below.)

As of today the releases are:
  BIND 9.4.1 (current official release)
  BIND 9.3.4 (maintenance release)
  BIND 9.2.8 (maintenance release with end of life August 2007) 

I was told that the CVS tags for the release branches are v9_2, v9_3 and 
v9_4 (for 9.2.x, 9.3.x and 9.4.x).

Comparing the Bv9ARM-book.xml for the different release branches doesn't 
seem good enough, as I am not sure if the features already existed but 
just not documented.

For example, v9_4 documents notify-delay but v9_4_1 does not.

Is comparing bin/named/config.c the best way?

(For config.c, v9_3 is same as v9_3_4, v9_2 is same as v9_2_8, and v9_4 is 
same as v9_4_1 so that makes it easy.)

Here is a start of my list. Please double-check this for me.

New in 9.3:

	recursing-file
	server-id
	tcp-listen-queue
	edns-udp-size
	dnssec-enable
	alt-transfer-source
	alt-transfer-source-v6
	multi-master
	max-journal-size
	ixfr-from-differences

Removed in 9.3:

	version
	allow-v6-synthesis

New in 9.4:

	allow-query-cache
	check-mx
	acache-enable
	acache-cleaning-interval
	max-acache-size
	dnssec-enable yes
	dnssec-validation
	dnssec-accept-expired
	clients-per-query
	max-clients-per-query
	zero-no-soa-ttl-cache
	notify-delay
	check-wildcard
	check-sibling
	check-integrity
	check-mx-cname
	check-srv-cname
	zero-no-soa-ttl
	update-check-ksk

New in 9.5

	allow-query-cache-on
	allow-recursion-on
	allow-query-on
	try-tcp-refresh

Does a list like this already exist?

Should I be looking at different source file?

  Jeremy C. Reed

p.s. I am doing this because I want to help improve the reference manual 
so an admin will know when features are added. This will make it easier 
for an admin to use one reference manual for different systems and will 
make it easier to learn new features (such as using maintenance release 
and moving to current official release). Also I think this may make it 
easier for ISC developers so they won't have to keep numerous different 
versions of ARM (because maybe one ARM can be used for all if it is clear 
on the differences).