Re: Best practices for changelogs
* Andres Mejia <email@example.com> [2007-11-14 23:27:39 CET]:
> The problem with this is that only the maintainer/uploaders is suppose
> to change anything with the package. Doing this requires the
> maintainer/uploaders uploading the package again. This would be a pain
> for those maintaining large packages like alien-arena-data or
If something gets changed it should be uploaded/offered again anyway? I
can't follow you. And besides the pain for large packages - it does
require only a reupload of the diff.gz, not the .orig.tar.gz, or would
it? If mentors.d.n doesn't work without uploading the .orig.tar.gz it is
seriously b0rked IMHO and people should just upload to some other
website they have access too.
> The changelog would contain only details about the packaging, so the
> information in a debian/changelog would most likely be irrelevant to a
> user anyway.
Erm, it isn't. The changelog contains informations about closed bugs,
for a start, which is immensly useful informations for users. Calling
the changelog irrelevant to a user is pretty blindfolded.