Simon McVittie writes ("Re: changelog practice, unfinalised vs UNRELEASED vs
~version"):
> On Mon, 13 Feb 2017 at 09:42:32 +1100, Ben Finney wrote:
> > I don't see how this complaint is any different from the need to merge,
> > for example, changes to API documentation and test cases that accompany
> > a functional change.
>
> It's the difference between "sometimes conflicts" and "always conflicts".
This is a very real problem for debian/changelog, but mergechangelogs
helps a lot. In any case as I say I'm not trying to mandate the
workflow where the changelog is updated as-we-go.
Ian.
