Anders Logg <[email protected]> writes: > I have made an attempt to add release notes for 1.3 (and also 1.0 and > 1.2 which were missing): > > http://fenicsproject.org/releases/ > > We need to do a better job with updating ChangeLog with meaningful > information. Most of what is written in the ChangeLog is very > low-level and does not make sense in a list of release notes. The > result is that the list of changes looks less impressive than it > actually is.
One approach is when you merge a branch to 'master', summarize the user and developer impact. You can do it either informally or with standardized tags, but either way, when preparing release notes, you use git log --first-parent v1.2..v1.3 This is a lot less cluttered than the entire history since it only contains merges, and if significant changes are announced here, it's easy to put them into an announcement. Note that for --first-parent to work properly, you have to avoid being an ungraceful looser of a merge race, e.g., https://bitbucket.org/fenics-project/dolfin/commits/45b1cd0b329b76f86587e19e738dc74a77678b4b https://bitbucket.org/petsc/petsc/wiki/developer-instructions-git#markdown-header-racy-integration
pgplo9RlqWmVW.pgp
Description: PGP signature
_______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
