On Wed, May 15, 2013 at 07:06:10PM +0000, Musayev, Ilya wrote: > > -----Original Message----- > > From: Chip Childers [mailto:chip.child...@sungard.com] > > Sent: Wednesday, May 15, 2013 2:40 PM > > To: dev@cloudstack.apache.org > > Cc: cloudstack-...@incubator.apache.org > > Subject: Re: [DISCUSS] RPM BUILD - Add change log from git > > > > On Wed, May 15, 2013 at 05:02:08PM +0000, Musayev, Ilya wrote: > > > Any thoughts on adding changelog into cloud.spec file pulled from git on > > the build? > > > > > > Something like the output of "git log -oneline". > > > > We can't assume that the build is happening based on a git repo. Our > > release > > is a source tarball that's an extract from the git repo. > > Then perhaps we can stage the changelog file? Either way, I have the solution > in my realm, I was just thinking it would be nice to know what happened > between release x.y and x.z. Something I've seen as common practice when you > get the package from another open source project. > >
We track the high level stuff in the CHANGES file, and we have the release notes publican docs. IMO the commit history isn't necessarily as useful, since it's kind of noisy in the end (with inconsistently useful commit messages). We have our release branches, and we have pushed tags to each branch that correspond to formal releases.
