Re: changelog practice, unfinalised vs UNRELEASED vs ~version
Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
> Q2: The information in the trailer line of the changelog entry in a new
> branch is not meaningful. Depending on the vcs etc. in use, it can
> cause pointless merge conflicts. Often the information is quite wrong:
> for example, a date which is earlier than the most recent commit. The
> Emacs changelog mode doesn't like editing finalised changelog entries.
> IME several of our tools deal badly with unfinalised changelog entries.
> For example, mergechangelogs mishandles them, and some parts of the
> package building toolchain sometimes complain. However, such bugs can
> be fixed and the fixes deployed fairly easily (via backports if
> necessary).
It also throws a bunch of Lintian errors, although I suppose that's
fixable as well. I really want something that will pass Lintian
completely but that dput will refuse to upload, which is what UNRELEASED
currently accomplishes.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: