@Anders: I agree that the change log is not well structured today. Should we try to include some more information for each feature too? Some example of usage or pointer to where a feature is used like a demo? Should we also include the date or revision for the added feature?
@Jed: What would happen with merges that are just fast forward, with no merge commit generated? It also looks like: git log --first-parent a788fefb92ba6f13335382d2c6d4c7aab56c9202..9b6f779ec7f3cf9d84e49258febbe4ad75d5d4bf includes a lot of non merge commits. Johan On Fri, Jan 10, 2014 at 9:43 AM, Jed Brown <[email protected]> wrote: > 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 > > _______________________________________________ > fenics mailing list > [email protected] > http://fenicsproject.org/mailman/listinfo/fenics > >
_______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
