Re: Documenting new upstream ver sion in ‘debian/changelog’ (was: Uploaded)
On Tue, 28 Apr 2009, Ben Finney wrote: Adeodato Simó d...@net.com.org.es writes: I hope you’ll agree that’s more useful for the person reading the changelog, and it only takes a bit more effort. No need to retroactively edit the changelog, though. The main reason to do this is because this is what the bug submitters get when their bug has been closed. I wholeheartedly agree with this, and would go further: even if there are no Debian BTS reports to close, you should *still* give the highlights of a new upstream version in the ‘debian/changelog’. It's perfectly fine if people do this, but it's not necessary to waste the time to document upstream changes which don't fix Debian bugs. The upstream changelog is there for a reason and duplicating information only serves to bloat the changelog. While #77375 is marked wontfix, it's not really an excuse to require documenting upstream changes in the Debain changelog. Things that want to show (or people who want to know about) upstream changes need to show the upstream changelog. Don Armstrong -- No amount of force can control a free man, a man whose mind is free [...] You can't conquer a free man; the most you can do is kill him. -- Robert Heinlein _Revolt in 2010_ p54 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Documenting new upstream ver sion in ‘debian/changelog’ (was: Uploaded)
Hi, On Tue, Apr 28, 2009 at 11:31:35AM +1000, Ben Finney wrote: I wholeheartedly agree with this, and would go further: even if there are no Debian BTS reports to close, you should *still* give the highlights of a new upstream version in the ‘debian/changelog’. I'm utterly uninformed by a bare “New upstream release.”; of course it's a new upstream release, I can already see that from the version number. This is a changelog, tell me *what changed* in this new upstream version. I don't see the need for this. For most packages upstream's changelog is installed in /usr/share/doc/$PACKAGE/, which will (hopefully) explain all you need to know. Of course, when you're closing bugs, I agree that there should be more verbosity than New upstream release. Cheers, Ryan -- _ Ryan Niebur ryanrya...@gmail.com signature.asc Description: Digital signature
