Re: changelog practice, unfinalised vs UNRELEASED vs ~version

[Guido Günther <agx@sigxcpu.org>]

On Sun, Feb 12, 2017 at 02:11:12PM +0000, Simon McVittie wrote:
[..snip..]
> with a middle ground that is less theoretically defensible than
> either, but pragmatically quite useful:
> 
> * Mostly write the changelog later, as in the second model.
>   Periodically summarize the changelog so far (since the last
>   commit to the changelog) and commit it as an UNRELEASED
>   changelog entry, providing a reference point.
>   `gbp dch --since=1234567` is useful for this model.

gbp dch also checks when the changelog was last touched so this mixed
mode should work without even using --since. This should help people
using a mixed model.
Cheers,
 -- Guido