[bind10-dev] maybe missing changelog entries?

[Jeremy C. Reed]

On Thu, 1 Mar 2012, Jelte Jansen wrote:

> > Maybe have one entry to introduce the multiple new lettuce tests?
> 
> Maybe I has misunderstood what goes into the changelog, but but for
> pure test additions, no features are added or changed, no bugs are
> (directly) fixed, and no compilation or installation issues are
> addressed, so none of the current categories for changelog entries are
> applicable.
> 
> So do we want to add such things to the changelog? And if so, should
> we add a [testing] category perhaps?


It may not be needed for the ChangeLog.  My concern is writing the 
release announcement and I use the ChangeLog to get ideas.

My other problem is that the ChangeLog entries don't always tell whole 
story. For example, we see different entries about DO bit in new query 
handler, NSEC3 bugfixes, etc., but nothing that summarizes to say: 
"b10-auth now supports signed zones in the in-memory data source."

A normal git log says "merged" and doesn't tell me what. (Can anyone 
share an quick and easy way to use git to better get logging?)

ChangeLog may not be needed, but I think we do need some way to announce
the big picture.

Maybe we should require merge commits should include a one-sentence 
description? (Not sure how that would work if merging from master to 
branch and then the pushing to master.)

> > 7be2f0a4db2e3e20ee28429fddea1dea11592eb7 what branch is this? NSEC3
> > related for new data source, maybe entry 384?
> > 
> 
> the commit message didn't adhere to our style (no branch number), but
> it looks like this was #1584 (and hence the changelog isn't needed
> since it was part of the NSEC3 feature addition)

Thanks!