On changelogs and version tracking
Recently a bug that was brought to my attention told me that I
should remind everyone about the importance of ordering of changelogs
in their package for the purposes of version control in the BTS.
Be careful when you reorder or add back changelog entries. If you
return to a previous version by means of an epoch (or something else)
you can either just tack the new upload/version at the top of the
changelog or elide the other entries in the changelog, and continue on
as before. Changelog entries should always be in upload order (which
presumably corresponds to chronological order) with the version upon
which this upload is based on immediately preceeding it.
If you don't do this, you end up with interesting version graphs like
As always, if you have any questions about the impact of changelog
order on the version tree or other similar questions, feel free to ask
on firstname.lastname@example.org or ask in #debbugs (OFTC) or ping me
(dondelelcaro) or any other debbugs person on IRC.
1: #403645, but it doesn't really matter
3: I should note that it's no big deal to fix these sorts of problems
up post-facto; it's just moderately confusing. ;-)
Americans can always be counted on to do the right thing, after they
have exhausted all other possibilities.
-- W. Churchill