Bug#65764: changelog shouldn't be in the copyright file
Josip Rodin <joy@cibalia.gkvk.hr> wrote:
> But forcing the maintainer to make a nice little summary and update it
> every time s/he makes a change in the upstream sources is not really
> what most of us want, or what most of our users need ;o) I'm known for
> making pedantic changes in stuff I package, but this is too much even
> for me :)
That's a fair argument. Actually, my position is neutral with respect
to this proposed change. I can see the list of modifications as useful
(and for many packages, the list will be simply, "added Debian GNU/Linux
package maintenance system files"); however, I can also see this as an
extra burden that may be unnecessary.
> A more general description of the important stuff that's changed in
> the behavior of the program in the package can/should still be found
> in README.Debian file.
In the behavior of the program, yes. That is definitely true.
> The changelog files are described like this in the Policy:
>
> <p> Document your changes and updates to the source package
> properly in the <tt>debian/changelog</tt> file.</p>
> Maybe we should define what is meant by "properly". Can someone (hint:
> a native speaker) propose a change to do this?
I think that this sentence is okay. It says everything; that is,
document the changes that you make for each release in the changelog
file. I don't see how we can improve on this.
If the developer is accurately maintaining a record of his or her work
on the package in the changelog file, then everything will be there.
- Brian
Reply to: