Re: changelog bug-closing should not be used unless the code changes
>>>>> "Ben" == Ben Collins <bcollins@debian.org> writes:
Ben> Just to comment on this little bit, I think it is
Ben> appropriate, because then the package's changelog serves as
Ben> sort of a FAQ if the issue is ever brought up again (and the
Ben> bug has expired from the BTS). It also keeps an historical
Ben> reference for decisions.
Just my 2 cents:
I thought the Changelog was used to record changes in the package.
Since when has the role of the Changelog also expanded to include the
role of the FAQ?
Surely, any questions like this belong in another file, FAQ.txt,
nonbugs.txt, or something, not the Changelog?
Who knows, perhaps we could mandate in policy "all users should check
the file /usr/share/doc/<package>/faq.txt before reporting a bug in
case the maintainer thinks it is a non-bug"[1]. Only this is
restrictive, it means a new package has to be released before the
faq.txt can be updated.
How about allowing maintainers to edit an area under
http://packages.debian.org.au/<package> which deals with common
problems users may have with the package? (I think this has been
suggested before). That way, users don't have to scan the entire BTS
history for the package to find out if the problem has either been
reported before.
Otherwise, you will end up with the full documentation appearing in
the Changelog, which is not the intended purpose of the Changelog.
--
Brian May <bam@debian.org>
Reply to: