[bind10-dev] Changes Log

[JINMEI Tatuya / 神明達哉]

At Thu, 1 Apr 2010 11:28:23 -0500 (CDT),
"Jeremy C. Reed" <jreed at isc.org> wrote:
> 
> We need to decide on the format or what to provide for a CHANGES file 
> and for release notes?
> 
> (I was hoping to talk about this on our phone call.)
> 
> Should we go with existing BIND 9 CHANGES style? This means we will have 
> to write them.
> 
> Should we create it automatically from svn log history? That will work 
> but some entries may be too verbose or not verbose enough.
> 
> The plan for now is to have a changes log included in the next tar ball 
> and in the release announcement.

I've not fully thought about it, but I'm afraid the current style of
BIND9 change logs is not very useful:

- the logs are often "too concise", and it wouldn't always be easy for
  a user to understand the severity of a bug or relevance to problems
  they're having.
- the definition of change categories ("bug", "func" etc) is not clear
- reference numbers to bug tickets (RT #xxxx) aren't useful for
  ordinary users because the BIND9 RT is closed

Some of the problems will be automatically solved in BIND10 due to its
nature of "broader openness", but some others may not be trivial to
address.  It might also depend on the expected target of the change
logs.  If it's mainly for users, we should probably provide more
informative logs; if it's mainly for developers, a simple one-line
summary with a reference to the bug ticket may suffice.

---
JINMEI, Tatuya