On Mon, Dec 02, 2019 at 11:21:12PM -0800, 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.

Well... I don't think there's anything good that can be done about the
entries about the unstable uploads that have happened in between...


Reply via email to