[bind10-dev] change log entries missing
Jeremy C. Reed
jreed at isc.org
Thu Sep 27 02:36:28 UTC 2012
On Wed, 26 Sep 2012, Jeremy C. Reed wrote:
> I see the last month has had many merges that aren't mention in the
> changelog.
>
I re-ordered some below:
> 2096
For libdns++ provide a lightweight (efficient) interface (RdataReader)
to iterate over RDATA (and RRSIG RDATA) encoded in memory.
> 2097
Define and Implement RdataSet class
> 2098
Define and Implement `TreeNodeRRset` class
> 2100
Update ZoneTable class
> 2107
redefine in-memory zone data
> 2108
redefine in-memory zone load()
> 2109
redefine in-memory zone finder (basic)
> 2110
redefine in-memory zone finder (wildcard)
> 2040
Prototype backend performance microbenchmark: Flat file
> 2143
Run benchmarks and write report
> 2151
well known "wildcard" LabelSequence
> 2161
remove old datasrc API code
Also 2163:
[meta] use signed RRset "as is" in Message
> 2165
update Message::addRRset() to be unaware of signedness
> 2180
tiny change; okay to ignore:
Warn administrator when creating an empty SQLite data source
> 2187
Remove "cout" statements from libdhcp++
Add this to the 474. entry?
> 2216
update query_bench so it will use the new data source config
> 2218
update InMemoryZoneFinder::findNSEC3 using memory-efficient version
> 2219
switch to memory-efficient version of in memory data source
> 2230
perfdhcp Documentation
This is substantial and should be mentioned.
> 2231
Allow sub-second timeouts in interface manager "receive" functions
> 2267
new generateRRsetFromIterator doesn't handle RRSIGs correctly
maybe no changelog entry since was a bug not in a previous release.
> 2272
Improve the perfdhcp command_options_helper code.
test case only?? If not, then add to 479. entry?
> 2282
implement specialized additional handling in in-memory data source
> I didn't look yet to see what is important above.
>
> Also I notice this need:
> - (Trac #1375, git 7ca65cb9ec528118f370142d7e7b792fcc31c9cf)
> + (Trac #1357, git 7ca65cb9ec528118f370142d7e7b792fcc31c9cf)
>
>
> We need a better way to ensure that everything is added. One way is to
> require some type of marking in git history that I can parse out. Or
> maybe we can require that every merge includes a changelog.
More information about the bind10-dev
mailing list