On Fri, May 17, 2013 at 07:35:33AM -0500, Tom Marble wrote:
> On 05/16/2013 08:18 PM, Richard Fontana wrote:
> > A summary of changes relative to the previous released verson shall be
> > provided in due course.
>
> FLOSS best practices generally suggest updating the CHANGELOG
> as you go -or- collecting highlights from commits since the
> last release in the CHANGELOG [0]. In this way such a release
> announcement comes with the answer to the question:
> "What changed in this release?"
I believe I started out with, or at least intending to maintain, a
CHANGELOG, and I have the vaguest memory of someone (Dave Neary?)
suggesting I use one. But I have been under the impression that
CHANGELOGs are rarely used by non-antediluvian FLOSS projects.
Depends if you have a strict definition of "CHANGELOG". Most popular
projects actually publish a list of changes on release so that users
know what to expect. Whether it's in the traditional form of a CHANGELOG,
or something fancier and/or more readable, doesn't really matter.
Regards
Antoine.