Paul Martz wrote:
I just committed what appears to be the first change to the 2.6 branch
post-release (see "[osg-submissions] Fix for PAT in FLT export").
Robert, how do you update the changeLog, are you just pulling it from
svn periodically or do you have some kind of automatic mechanism in
place? My concern here is that we track the changes to the 2.6 branch
so that when/if we do a 2.6.1 release, we can easily create release
notes that describe what went into it.
I find Changelogs hard to read, usually due to cryptic log entries. Plus
there's more in the log than needs to be in the release notes (and vice
versa).
I think writing release notes as we go is the easiest. We can continue
to keep the current style of commit messages.
For (automatically) keeping track of merges between branches I'd once
again would like to point out svnmerge
(http://www.orcaware.com/svn/wiki/Svnmerge.py). It not only keeps track
of which revisions have already been merged and which ones are left to
be merged for a branch, but it also produces commit messages that
contain the original log entries of the revisions that got merged.
Paul M
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
