[Quilt-dev] Changes file

[Jean Delvare]

Hi all,

Can we get rid of quilt.changes? It's a pain to maintain, I keep
forgetting adding entries to this file and I'm sure I'm not alone. And I
think it's essentially redundant with git log.

I know we're using quilt.changes to feed the changelog in quilt.spec,
but I don't think it makes any sense either. Rpm changelogs should
contain high level user-visible change information and packaging change
information, not a list of low level changes. That's what source code
management tools are for.

In most projects I work on, we have given up on the per-commit changelog
file long ago. I think a high level CHANGES file with entries grouped by
area (rather than time line) is much more useful, for example
lm-sensors' CHANGES file:

http://www.lm-sensors.org/browser/i2c-tools/trunk/CHANGES

But we could even go without a real-time CHANGES file at all, and
user-visible changes are simply announced when a new version is released
(and possibly stored in a CHANGES file for the record then.)

Opinions?

-- 
Jean Delvare
Suse L3 Support