On Tuesday, 25 December 2012 at 11:15:17 UTC, Jonathan M Davis
wrote:
On Tuesday, December 25, 2012 03:07:35 Walter Bright wrote:
On 12/24/2012 9:03 AM, Jonathan M Davis wrote:
> How about the very example that I gave about specifically
> providing a note
> to developers about the impending changes to std.format? No
> bug had been
> fixed, and no enhancement request had been implemented. No
> code change
> had even taken place yet. It was a note about a future
> change that
> developers needed to be made aware of.
Well, a future change shouldn't be in a *change* log any more
than it should
be in bugzilla.
What you're talking about should be called "release notes".
If you want to be pedantic about it, sure. But we don't have
release notes
separate from the changelog at this point. And while some
changes which aren't
currently put in bugzilla _could_ be put there (e.g. the
addition of a new
module), that doesn't necessarily mean that they belong there.
So, while
automating the list of bug fixes makes good sense, having a
section of the
changelog or release notes or whatever which is written by
humans also makes
good sense.
Lots of projects take the changelog from the SCM log instead,
which is the REAL changelog. Of course to do that you have to
write good commit messages...
