On 03-12-2019 08:21, Russ Allbery wrote:
> Paolo Greppi <paolo.gre...@libpf.com> writes:
>> What is the best approach for d/changelog when releasing a package to
>> unstable after it has been through a few iterations to experimental ?
>> It would seem that the right thing to do is to keep all experimental
>> changelog entries, and add a new one for unstable.
> This is the typical practice, including all the intermediate experiments
> or false starts in experimental.
> I sympathize with wanting to clean up some of that, but as a project we
> generally have decided to live with that.  Most users don't read the full
> changelog anyway (user-visible notes should be in NEWS instead, which are
> shown to more people via apt-listchanges), and removing versions from the
> history has bad effects on the bug-tracking system, historical archives,
> etc.

The bts parses the changelogs to determine the history of packages. So
it's really the best to always keep the changelog entries that are part
of the history of the version of the package. So, if you upload a
descendant of the package in experimental, the changelog of the
experimental changes really should stay.


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to