I think just the changes is better and easy to generate per release unless a separate file is maintained.
maybe this f a less verbose variant git log v0.7.0..v0.8.0 But lets agree now on something so that for 0.9.0 we at least can build debian packages, we can fine tune later. On 21 January 2015 at 11:43, Steve McIntyre <[email protected]> wrote: > On Wed, Jan 21, 2015 at 07:25:58PM +0300, Maxim Uvarov wrote: > >On 01/21/2015 06:56 PM, Steve McIntyre wrote: > > > >>I'd argue that over time we should be keeping a summary changelog > >>anyway, something that will be trivially includable in the > >>debian/changelog file before we release. We should be doing this for > >>end users who are not tracking us via git... > >> > >>Cheers, > >why not put there output from > >git log --oneline > > I think that it's a bit verbose, even then: > > tack:~/linaro/odp/odp$ git log --oneline | wc -l > 653 > > We have a lot of small changes that probably don't merit being called > out individually. More useful would be a shorter list of new APIs that > are added, major bugs fixed etc. > > Cheers, > -- > Steve McIntyre [email protected] > <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs > > > _______________________________________________ > lng-odp mailing list > [email protected] > http://lists.linaro.org/mailman/listinfo/lng-odp > -- *Mike Holmes* Linaro Sr Technical Manager LNG - ODP
_______________________________________________ lng-odp mailing list [email protected] http://lists.linaro.org/mailman/listinfo/lng-odp
